Menu
Systematic root-cause debugging workflow from reproduction through regression-test verification.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Shared protocol for review-shaped actions, authorization scope, defect routing, L2 audit handling, and local-only capture.
Use when the user asks to "test TPC-H", "check compliance", "review architecture", "run quality checks", "check binaries", "test dialect translation", "compare implementations", "run live platform tests", or "plan and execute" a benchmark feature.
Use for "commit code", "review code", "fix lint/type error", "improve performance", "compare code", "shrink code", "generate spec from code", "investigate code", "debug an error", "triage a bug", "iterate to green", or "create handoff prompt".
Use when the user asks to "create documentation", "build docs", "review docs", "compare documents", "compress docs", "adversarial review docs", or "commit docs".
Use when the user asks to "sync skills", "set up skill-sync", "check skill status", "validate skills", "preview skill changes", "diagnose skills", "pin a skill", "unpin a skill", "prune skills", or "promote skill changes".
Use when the user asks to "run tests", "create tests", "fix failing test", "add test coverage", "fix slow tests", or "commit test changes".
| name | debug-framework |
| description | Systematic root-cause debugging workflow from reproduction through regression-test verification. |
Stop feature work when something breaks: preserve repro, diagnose, fix root cause, guard, verify, then resume.
Apply SHARED/plan-deepening-framework/SKILL.md Layer 3: confirm the stated bug is the actual constraint, not an upstream symptom. Document any reframe.
Prefer the narrowest effective scope:
Host capacity changes are escalation. Document skipped rungs when relevant.
A blocker requires all three: root cause known, applicable fix rungs tried or ruled out with concrete reasons, and remaining fix outside agent authority (upstream, credentials, user hardware/capacity, or explicit policy/architecture decision).
Reproduce before fixing; fix causes not symptoms; keep blast radius narrow; make unrelated changes only with explicit authorization.
