debugging
From the author
Systematic 4-phase debugging with root cause investigation. Use when fixing bugs to prevent random fixes.
Install
npx skills add tmcfarlane/team-avatar --skill debugging -a claude-code
Installs to .claude/skills/debugging/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
Security100
Provenance65
Maintenance100
Licence100
Adoption35
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- systematic-debuggingcbrock84/headcountFinds the root cause of a bug, test failure, or unexpected behavior before proposing any fix. Use this whenever something is broken and the cause is not yet proven — a failing test, a production error, intermittent behavior, or a symptom that appeared after a change. Also use when a fix has been attempted and did not work, or when the same bug keeps coming back.Engineering★ 2.1K
- debug-systematictravisjneuman/.claudeSystematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.Engineering★ 106
- debugging-strategieswshobson/agentsMaster systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.Engineering★ 41.7K
- debuggersickn33/agentic-awesome-skillsDebugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.Engineering★ 48.5K
- debugging-methodologyDevelopersGlobal/ai-agent-skillsSystematic root cause analysis for production and development bugs. Hypothesis-driven debugging — never guess-and-check.Engineering★ 215
- debugging-and-error-recoveryaddyosmani/agent-skillsGuides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need to figure out what broke and why — a systematic approach to finding and fixing the root cause rather than guessing.Engineering★ 110.3K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in