From devrites
Debug systematically when tests, builds, or runtime/browser checks fail — deterministic feedback loop, reproduce, 3-5 ranked hypotheses, instrument, fix root cause, regression-test. Use when the user says "debug this", "why is it failing", "it broke", "the build is red", "the tests fail". Not for code review or flaky tests (fix the flake first).
How this skill is triggered — by the user, by Claude, or both
Slash command
/devrites:devrites-debug-recoveryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Disciplined recovery from failures. **NO shotgun edits, NO blanket retries.**
Disciplined recovery from failures. NO shotgun edits, NO blanket retries.
Loaded by /rite-prove (and during /rite-build) when something fails. Use
when tests, builds, typecheck, runtime, or browser checks are red and the next
move is unclear.
/rite-plan repair).devrites-doubt, or ask the user. Don't keep trying
variations of a wrong idea.npx claudepluginhub viktorsbaikers/devrites --plugin devritesGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.