Everyday moves
- 01Debugging and fixing a bug9 min
A precise reproduction command and a complete stack trace steer the diagnosis towards the real cause of a bug, and the fix is only declared closed once a regression test reproducing the faulty case has been run and its output read.
- 02Building and refactoring with tests first10 min
Claude Code examines the test files already present in a project to write a new test in the same style before the implementation, and confirming that this test genuinely fails proves it does indeed test something that does not exist yet.
- 03Reviewing code and driving git in natural language10 min
Local code review through /code-review offers five effort levels from low to max, and ultra is not a sixth level of the same scale but a distinct facility, a multi agent review in the cloud billed separately.
- 04Getting to grips with, documenting and migrating a codebase10 min
On an unfamiliar repository, asking for an overview before making any changes shapes the questions that follow, and the /init command actually reads the project's content to write a first CLAUDE.md rather than starting from a blank page.
- 05Automating a repetitive task and writing a throwaway script8 min
Automating a repeated action starts with separating what stays fixed from what varies each time, is described by its input, its output and the environment it must run in, and is checked with a dry run before any step that deletes, moves or overwrites anything.
- 06Quick terminal moves12 min
A handful of short moves cover most of a day to day session: resuming a specific session, going back to an earlier checkpoint, running a shell command without leaving the conversation, and asking for deeper reasoning for a single turn without changing the setting for the whole session.
- 07Headless mode, output styles and background tasks9 min
Headless mode runs Claude Code without an interactive interface using -p, --output-format determines whether the output stays plain text or becomes a JSON object a script can use, with the total cost included, and run_in_background lets a long command keep running without blocking the conversation.
- 08Running in parallel: worktrees, model and fast mode10 min
A git worktree isolates a parallel session on its own branch, and the --worktree flag now automates the whole thing, where previously only the manual git worktree add gesture existed.
- 09Writing pitfalls: files, parallel edits and lost deliverables11 min
A success report written by a sub-agent proves nothing about the real state of files, since it starts in an isolated context with no access to what the main agent has already read or written, and the only reliable proof remains a diff checked afterwards, not the text of the report.