Chapter C66 · Interactive Course
Claude Code use cases and recovery
Exploring a path, repairing a bug, narrow tests, refactors, documentation from real code, and stalled sessions.
Core Learning Concept
Review the fictional Claude Code result through the source, diff, command output, and task requirements. Identify what was explored, changed, and verified. If work stalled, inspect the last confirmed state before retrying. Finish with a clear handoff rather than relying on the agent’s closing statement.
What You’ll Learn in This Chapter
-
Explore an unfamiliar code path
Request an explanation tied to source locations.
To explore unfamiliar code, ask a focused question and follow the path through entry points, functions, and data boundaries. Require references that can be checked in the project. A useful explanation connects those pieces to behavior. It should distinguish what the source proves from runtime behavior that still needs testing.
-
Repair a reproducible bug
Guide a small behavior change.
A reproducible bug has a known trigger and an expected result. Give the agent that evidence, let it inspect the responsible path, and judge the repair against the original behavior. Re-run the reproducer and relevant nearby cases. Changing code without checking the trigger leaves the diagnosis unverified.
-
Add a narrow test
Ask for coverage of a specified behavior.
A narrow test should protect a meaningful behavior, such as rejecting a missing required field. Use representative inputs and assertions that match the requirement. Avoid tests that merely echo implementation details. Review whether the test would catch the intended failure before treating a passing result as sufficient evidence.
-
Refactor while preserving behavior
Separate internal changes from feature changes.
Refactoring changes internal structure while preserving external behavior. Establish the contract first, inspect the diff for unintended changes, and run regression checks. Cleaner-looking code can still alter edge cases without rigorous verification.
-
Write documentation from verified code
Tie a guide to the implemented interface.
Documentation must describe verified code and working procedures. Inspect the implementation and verify all commands directly. A readable guide with invented setup steps is worse than a shorter guide whose instructions are fully confirmed.
-
Recover from a stalled session
Choose resume, narrower context or a focused error check.
A stalled session may be waiting on a command, missing input, or facing a failed step. Inspect the current process or task state before restarting. Preserve completed work and check external effects before retrying writes. A recovery report should name the last verified result and the next useful action.
-
Review a Claude Code result
Inspect a bug-fix transcript for scope, patch, tests and remaining limitations, then write one concise follow-up correction.
-
Complete a Claude Code practice run
Follow a supplied version-labelled session through workspace choice, loaded guidance, tool actions and a report of what was actually validated.