I often use simple prompts like “make it faster” and get back functionally correct commits. When I review them, I often discover that they didn’t do what I really wanted - sometimes Claude made it faster by incurring expensive costs, or doing a migration that would be risky in prod, or making a tradeoff that’s not worth it.

Perhaps I could set up a workflow to handle this without reading the code. I’ve seen people who make Claude fill out arcane templates, and then spend their time reviewing reports and tinkering with loops or whatever. But why would I want to read a TPS report about the code rather than just reading the code?