Debug
Auditable, portable agent skills that turn open-source maintenance - review, debugging, verification, handoff - into repeatable workflows for Codex, OpenCode, and Pi
npx -y skills add sainzs/santiagosainz-skills --skill debugAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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 a failing command, bug, flake, runtime error, wrong output, or performance regression with evidence: reproduce, minimize, hypothesize, instrument, fix, and regression-test. Use when the user asks to debug, diagnose, fix a failure, or use debug-loop.
SKILL.md
1.8 KB, as published. Nobody here has run it
debug
Find root cause before changing code.
Unix/Pi Contract
- Do one job: turn a symptom into root cause, fix, and regression proof.
- Consume an exact repro, logs, runtime state, and code path; emit cause, patch, and proof.
- Keep output bounded: inspect high-signal tails, focused files, and direct repros.
- Use shell and repo-native tools first; use heavier tooling only when it improves observation.
- After two identical failures, change hypothesis or instrumentation.
Use
Use for failing tests, CI failures, crashes, hangs, flakes, broken UI flows, bad output, slow paths, and environment drift.
Workflow
- Reproduce the symptom with the exact command, URL, or workflow.
- Minimize to the smallest failing surface.
- State one current hypothesis and the evidence that would disprove it.
- Inspect the code path and runtime state that can affect the symptom.
- Add temporary instrumentation only when observation is otherwise impossible; remove it before finishing.
- Fix the root cause, not just the observed error string.
- Add or identify a regression proof and rerun the original repro.
Guardrails
- Do not guess from logs alone when a repro is available.
- Do not widen the fix until the local cause is understood.
- Treat hangs and concurrency failures as first-class symptoms; use timeouts, logs, and serialized repros.
- Separate pre-existing unrelated failures from failures caused by the edit.
Output
Return:
- Symptom and repro.
- Root cause.
- Fix.
- Regression proof.
- Commands and results.
- Remaining risks or external blockers.