Case Study: Shipping a Fix with Claude Code, End to End
A single incident, one continuous session, and every mechanism in the track put to work
Follow one bug — CSV exports intermittently missing rows in a TypeScript/Node monorepo — from a ten-minute setup audit through exploration, a wrong hypothesis, a checkpoint recovery, implementation, a workflow that generalizes the fix, a PR with /code-review, CI, and a follow-up routine. Every decision is named, justified, and linked back to the track subject that owns it, so you can see the whole toolkit working together instead of one mechanism at a time.
Practice questions (8)
-
View →
Reworking Phases 2–4 When There Is No Test Suite
Advanced · Free -
View →
If the First Hypothesis Had Been Right
Advanced · Free -
View →
Re-Planning the Incident for a Three-Person Team
Advanced -
View →
Cutting Work Under a Hard Cost Cap
Advanced -
View →
Pipelining a Safe Mass-Fix When the Audit Finds Six More Instances
Advanced