debugging-and-error-recovery
Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
Security Assessment
Detected risks:
About debugging-and-error-recovery
The 'debugging-and-error-recovery' skill is designed to help developers systematically identify and resolve errors in their code, builds, tests, or runtime environments. Rather than relying on guesswork, this skill enforces a structured approach to diagnosing and fixing problems. It emphasizes the importance of stopping feature development when an unexpected error occurs, preserving all relevant evidence such as logs and error messages, and carefully analyzing the issue to determine its root cause. By following this methodology, users can avoid compounding errors and ensure that fixes are both effective and sustainable.
Key features of this skill include a detailed triage checklist for systematic debugging, strategies to reproduce failures reliably, techniques to localize the source of an issue across different layers (UI, backend, database, build tooling, external services, or tests), and methods to reduce complex problems to minimal reproducible examples. Additional practices such as bisection for regression detection and environment-specific debugging strategies help streamline the process and increase confidence in solutions. The skill also provides concrete examples for running failing tests and isolating issues, making it practical and actionable for daily development workflows.
This skill is especially useful for software engineers, QA testers, DevOps professionals, and anyone involved in maintaining or debugging codebases. Common use cases include test failures after code changes, build errors, unexpected runtime behavior, or incidents reported in production. By providing a consistent framework for error recovery, this skill aids teams in maintaining code quality, reducing downtime, and improving overall reliability of software systems.
FAQ
When should I use the debugging-and-error-recovery skill?
Use it whenever tests fail, builds break, runtime behavior doesn't match expectations, or any unexpected error occurs. It is intended for systematic root-cause analysis rather than guesswork.
Which environments or languages is this skill compatible with?
The skill is language-agnostic and can be applied to various development environments, including frontend, backend, databases, build systems, and CI/CD pipelines, as long as failures can be reproduced and logged.
Can I skip steps in the triage checklist?
No. Skipping steps can lead to incomplete diagnosis and potentially compounded errors. Each step, from reproduction to localization and reduction, should be followed in order.
What if a bug cannot be reproduced reliably?
Investigate timing-, environment-, or state-dependent conditions. Use logging, artificial delays, isolation, and monitoring to gather enough evidence to diagnose intermittent issues.
Does this skill replace code reviews or testing practices?
No. It complements existing testing, code review, and quality assurance practices by providing a structured approach to debug and fix issues when they arise.
Install debugging-and-error-recovery
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
addyosmani/agent-skills