Home

Everyday moves

1. 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.

2. 02Building and refactoring with tests first10 min

   Ask for the tests before the implementation, then run the test runner to confirm they genuinely fail: red proves the test can fail, green proves the implementation satisfies it. Claude reproduces the style of the tests already in the repository, and the refactor then moves one concern at a time.

3. 03Reviewing code and driving git in natural language10 min

   /code-review launches a local review with effort levels from low to max, and ultra is not one of them: it is a distinct facility, a multi-agent review in the cloud, billed separately. Git is then driven in plain language, with the same permission safety net as commands typed by hand.

4. 04Getting to grips with, documenting and migrating a codebase10 min

   On an unfamiliar repository, start by asking for an overview before any change: it shapes the questions that follow. The /init command actually reads the repository's content to produce a first CLAUDE.md, a first draft to reread and trim, and migration or documentation work ends with a review of the final diff.

5. 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.

6. 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.

7. 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.

8. 08Running in parallel: worktrees, model and fast mode10 min

   A git worktree opens a second checkout of the repository on its own branch, so Claude Code sessions can work in parallel without overwriting each other. The claude --worktree command creates it automatically. In each worktree, the model is chosen on difficulty, and fast mode on cost.

9. 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.