4 ms·
Every time Claude Code finishes a task, I plan a full review of its own task with a very detailed plan and it catches itself many things it didn’t see before. I
by shinycode 10mo ago
Every time Claude Code finishes a task, I plan a full review of its own task with a very detailed plan and it catches itself many things it didn’t see before. It works well and it’s part of the process of refinement. We all know it’s almost never 100% hit of the first try on big chunks of code generated.
- a24j 10mo agoHow exactly do you plan/initiate a review from the terminal? open up a new shell/instance of claude and initiate the review with fresh context?
- deleted 10mo ago[deleted]
- fragmede 10mo agoYeah. It dumps context into various .md files, like TODO.md.
- shinycode 9mo agoIt depends on the task but I have different Claude commands that have this role, usually I launch them from the same session. The command has the goal of doing an analysis and generating a md file that I can execute with a specific command and the md as parameter. It works quite well. The generated file is a thorough analysis of hundred of lines with specific coded content. It’s more precise that my few line prompt and help Claude stay on rails