Bugfix And Regression Evidence — Claude Code Guide

A bugfix needs regression evidence

A regression check captures the behavior that failed and prevents the same defect from returning silently. Pair it with an adjacent positive scenario when the boundary is important.

Do not claim a regression result until the check has actually run.

Bugfix sequence

1. Reproduce the failure.
2. Add or identify a focused regression case.
3. Make the minimal fix.
4. Run regression and adjacent checks.
5. Inspect the diff and changed files.
6. Record actual output and remaining risk.

Bugfix handoff

Symptom: <failure>
Reproduction: <command or scenario>
Fix: <minimal change>
Checks run: <actual commands>
Result: <actual output>
Remaining risk: <list>
Status: documented example unless evidence is attached.