Debug Systematically
Diagnose software failures systematically instead of guessing. Use for bugs, failing tests, unexpected output, crashes, regressions, and inconsistent behavior.
Install
/plugin marketplace add cellrishi-code/claude-skills-atlasThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add cellrishi-code/claude-skills-atlas --skill debug-systematicallygit clone --depth 1 https://github.com/cellrishi-code/claude-skills-atlas.git /tmp/claude-skills-atlas
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills-atlas/skills/coding/debug-systematically ~/.claude/skills/debug-systematicallyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Debug Systematically Treat debugging as evidence gathering and hypothesis elimination. ## Process 1. Reproduce the failure when possible. 2. Capture the exact error, input, environment, and expected behavior. 3. Minimize the failing case. 4. Trace backward from the observable failure to the earliest incorrect state. 5. Generate a small set of competing hypotheses. 6. Test the cheapest hypothesis that can distinguish them. 7. Apply the smallest correct fix. 8. Re-run the original reproduction and relevant regression tests. 9. Explain the root cause, not only the patch. ## Rules - Never change multiple unrelated things before verifying the cause. - Do not replace an error with silent fallback behavior unless intended. - Preserve useful diagnostic information. - Treat intermittent failures as evidence about timing, state, concurrency, caching, or environment. - If the cause cannot be established, label it unresolved rather than guessing. ## Output Return: - Reproduction - Observed vs expected behavior - Root cause - Minimal fix - Verification - Remaining uncertainty ## Purpose Diagnose software failures systematically instead of guessing. Use for bugs, failing tests, unexpected output, crashes, regressions, and inconsistent behavior.. ## When to use Use this skill when the task involves debug systematically and the user needs a structured, repeatable approach. ## Instructions
Details
- Skill name
debug-systematically- Repository
- cellrishi-code/claude-skills-atlas
- Path
skills/coding/debug-systematically/SKILL.md- License
- MIT
- Repo updated
- 13 November 2026
FAQ
What does the Debug Systematically skill do?
Diagnose software failures systematically instead of guessing. Use for bugs, failing tests, unexpected output, crashes, regressions, and inconsistent behavior.
How do I install the Debug Systematically skill?
Claude Code plugin: /plugin marketplace add cellrishi-code/claude-skills-atlas. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Debug Systematically popular?
It lives in cellrishi-code/claude-skills-atlas, which has 5 GitHub stars and 6 forks.
Related skills
Atlas
5cellrishi-code/claude-skills-atlas
Use the Claude Skills Atlas as a reusable library of skills, prompts, workflows, agents, and templates. Activate when a task can benefit from a pre-made workflow or reusable instruction set.
Codebase Explorer
5cellrishi-code/claude-skills-atlas
Use when entering an unfamiliar codebase and you need to understand architecture, entry points, dependencies, conventions, and data flow before editing.
Codebase Understanding
5cellrishi-code/claude-skills-atlas
Build a reliable mental model of an unfamiliar repository before making changes. Use when entering a new codebase, investigating architecture, or when the user asks where a feature belongs.
Implementation Planner
5cellrishi-code/claude-skills-atlas
Use when a coding task is large enough to require repository inspection, a plan, affected files, risks, and verification before implementation.
Implementation Review
5cellrishi-code/claude-skills-atlas
Review an implementation against its requirements, repository conventions, correctness risks, tests, and maintainability. Use before opening a pull request or when reviewing completed work.
Adr
9tarunccet/pm-skills
Document architecture and product decisions using the Nygard ADR format — captures context, alternatives considered, and consequences so the team never asks 'why did we do it this way?' again. Use when making architecture decisions, choosing between technical approaches, selecting vendors, or any decision that will be hard to reverse.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.