debugging-recovery Skill
Systematic debugging with structured triage. Use when tests fail, builds break, runtime behavior does not match expectations, or any unexpected error occurs during implementation. Do not use for planned refactoring (use code review), for test strategy (use test-discipline skill), or for security-specific issues (use se Published by microsoft in devsquad-copilot.
What is debugging-recovery Skill?
Systematic debugging with structured triage. Use when tests fail, builds break, runtime behavior does not match expectations, or any unexpected error occurs during implementation. Do not use for planned refactoring (use code review), for test strategy (use test-discipline skill), or for security-specific issues (use se Published by microsoft in devsquad-copilot. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Security review
- Testing use cases
- Security review use cases
Technical details
- Install or run with Copy skill directory
When to use debugging-recovery Skill
- Use it for testing.
- Use it for security review.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/devsquad-copilot
- Skill file: .github/plugins/devsquad/skills/debugging-recovery/SKILL.md
What it does
Systematic debugging with structured triage. Use when tests fail, builds break, runtime behavior does not match expectations, or any unexpected error occurs during implementation. Do not use for planned refactoring (use code review), for test strategy (use test-discipline skill), or for security-specific issues (use se
Skill instructions
Debugging and Error Recovery When to Use - Tests fail after a code change - The build breaks unexpectedly - Runtime behavior does not match expectations - An error appears in logs or console during implementation - Something worked before and stopped working - An agent did something its spec, manifest, or oversight model did not authorize (see "Agent-Originated Failures" below) Stop-the-Line Rule When anything unexpected happens during implementation: 1. STOP adding features or making further changes 2. PRESERVE evidence (error output, logs, reproduction steps) 3. DIAGNOSE using the triage checklist below 4. FIX the root cause, not the symptom 5. GUARD against recurrence with a regression test 6. RESUME only after verification passes Do not push past a failing test or broken build to work on the next feature. Errors compound. A bug in step 3 that goes unfixed makes steps 4-10 wrong. Failure Source Classification Before running the triage checklist, decide whether the failure is agent-o
Explore related resources
Frequently asked questions
What is debugging-recovery?
debugging-recovery is a open-source AI agent skill with Copy skill directory. Systematic debugging with structured triage. Use when tests fail, builds break, runtime behavior does not match expectations, or any unexpected error occurs during implementation.
Who is debugging-recovery best for?
debugging-recovery is best for reusing agent instructions, scripts, and references, testing workflows, security review workflows.
How do I install debugging-recovery?
Install or run debugging-recovery using Copy skill directory. Check debugging-recovery for the latest setup command.
Is debugging-recovery actively maintained?
debugging-recovery may need a closer maintenance check before production use.
Auto-fetched from GitHub.
