Chapter 10 · CLI
Daily workflow: reading code, planning, editing and testing
Daily work with Claude Code runs in a loop: understand the relevant code, plan, make a small change and test. Keeping the loop short and controlled is what makes the tool reliable.
Video
Steps
- Start a task with understanding: ask the tool to locate and explain the relevant code before changing it.
- Plan in plain language and split a big task into small steps you can verify separately.
- Make one change at a time and review the diff before approving; big scattered changes are hard to review.
- Run tests after every change and let the tool fix failures; green tests are a condition for continuing, not a bonus.
Common pitfall: One giant request like build the whole feature produces a giant diff nobody can review; small steps end up faster.
Hands-on exercise: Pick a small bug in your project and walk the full loop: understand, plan, change, test. Record how long each step took.
Filmed demo · Video is added in the media phase
Recap
Comprehension check
What is the recommended structure for a task with Claude Code?
Recap
- Understand before changing
- One small change at a time
- Green tests are a condition to continue