One Claude Code Tip a Day: Snapshot the Starting Diff
Before Claude Code edits a dirty working tree, snapshot the starting diff, label what is already there, and make every later review separate your changes from the model’s patch.
Read moreAI Coding
A collection of 61 posts
One Claude Code Tip a Day: Build a Hypothesis Table Before Editing
Before Claude Code patches a bug, make it list competing hypotheses, evidence, checks, and the smallest next action. The table keeps debugging honest when the first theory sounds too convenient.
Read more
One Claude Code Tip a Day: Run a Post-Edit Traceback
After Claude Code edits, make it trace every meaningful change back to the failing behavior, the file evidence, and the verification result before you accept the patch.
Read more
One Claude Code Tip a Day: Ask What Claude Did Not Read
Before trusting a Claude Code plan or patch, ask it to name the files, runtime paths, logs, and assumptions it did not inspect. The unread list turns confidence into reviewable scope.
Read more
One Claude Code Tip a Day: Draft the Plan in /ultraplan Before the Patch
Use /ultraplan when the work is too large for a casual prompt: draft the plan separately, attack its assumptions, then bring back only a verified first slice.
Read more
One Claude Code Tip a Day: Use /simplify After the Feature Works
After a feature works, run /simplify as a separate cleanup pass: preserve the proof, narrow the target, review the diff, and reject clever rewrites that change behavior.
Read more
One Claude Code Tip a Day: Turn GitHub Issues Into Debuggable Tasks
Use Claude Code to decompose a vague GitHub issue into small, verifiable tasks before asking it to edit files.
Read more
One Claude Code Tip a Day: Treat Deletions as High-Risk Edits
When Claude Code deletes code, slow the session down: ask what each removal proves, which runtime path depended on it, and what verification would catch a bad cleanup.
Read more
One Claude Code Tip a Day: Set a Change Budget Before Editing
Before Claude Code edits, give it a change budget: the files it may touch, the checks it must run, and the conditions that require stopping instead of expanding scope.
Read more
One Claude Code Tip a Day: Make /verify Earn Its Keep
Use /verify as a structured evidence pass: define what should be proven, let Claude run the app and checks, inspect the failures, then make one correction before you trust the fix.
Read more