Diagnose loop
Portable AI-engineering skills for Claude Code, Codex, and coding agents: bounded scope, mini-specs, vertical slices, verification, ship gates, and handoff.
npx -y skills add tmusser/ai-engineering-skills --skill diagnose-loopAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Debug failures systematically.
SKILL.md
1.1 KB, as published. Nobody here has run it
Diagnose Loop
Purpose
Debug failures systematically.
When to use
Use when a command fails, behavior is wrong, a test regresses, or output does not match the spec.
Inputs
- Failure report
- Exact command or reproduction case
- Recent changes
- Logs, traces, or output
Workflow
- Freeze feature work.
- Reproduce the failure.
- Identify the exact failing command or case.
- List hypotheses.
- Instrument minimally.
- Apply the smallest fix.
- Add a regression check if possible.
- Rerun the original failing command.
- Rerun relevant verification.
Outputs
- Root-cause note
- Smallest fix
- Regression check when possible
- Rerun results
Stop conditions
- The original failure is fixed and verified.
- The failure cannot be reproduced.
- The next step requires a product or data decision.
Anti-patterns
- Randomly editing files before reproducing the bug.
- Fixing symptoms without naming the failing case.
- Adding noisy instrumentation and leaving it behind.