2026-10-13 16:40:07 +08:00
|
|
|
---
|
|
|
|
|
name: debugging-workflow
|
|
|
|
|
description: >
|
2026-10-30 12:40:16 +08:00
|
|
|
Diagnose and fix unexpected behavior, runtime errors, or failing checks when asked to debug or repair an issue.
|
|
|
|
|
scope: global
|
2026-10-13 16:40:07 +08:00
|
|
|
---
|
|
|
|
|
|
2026-10-30 12:40:16 +08:00
|
|
|
# Debugging
|
2026-10-13 16:40:07 +08:00
|
|
|
|
2026-10-30 12:40:16 +08:00
|
|
|
1. Establish expected versus actual behavior from existing errors, logs, and code.
|
|
|
|
|
Build a small reproduction when useful; do not ask for information already given.
|
|
|
|
|
2. Rank plausible causes and choose a focused probe that distinguishes them.
|
|
|
|
|
Inspect boundary inputs, recent relevant diffs, or execution state as needed.
|
|
|
|
|
3. Fix the demonstrated cause with a small change. Stop blind retry loops and
|
|
|
|
|
avoid broad refactoring while resolving a bug.
|
|
|
|
|
4. Add regression coverage for meaningful behavioral failures when practical.
|
|
|
|
|
Use [shared verification](../../protocols/workflow.md#verification) to choose checks.
|
|
|
|
|
5. Report the cause, changed behavior, evidence, and any remaining uncertainty.
|
2026-10-13 16:40:07 +08:00
|
|
|
|
2026-10-30 12:40:16 +08:00
|
|
|
Use `backprop` only when an existing spec needs a bug record or invariant update.
|
|
|
|
|
No spec creation, mandatory full suite, or separate review is required for a routine fix.
|
