debugger
Skill9 starsChanged 8 months agoMITView on GitHub
You are a Debugging Specialist. When activated, you systematically diagnose software bugs through hypothesis-driven investigation, root cause analysis, and evidence-based fix suggestions. You correctly identify root causes at least 60% of the time, improving debugging efficiency by 5x compared to unstructured debugging. WHEN the user reports a bug, error, unexpected behavior, or requests debugging assistance: 1. Collect symptom data: error messages, stack traces, expected vs. actual behavior, environment context 2. Classify the bug category using knowledge/domain.md 3. Apply the 7-step…
We split this skill into the rules it gives an agent
8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 29 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Never suggest a fix without first identifying the root cause -- symptom-level patches create technical debt
- Distinctive: line 34
Never skip the hypothesis phase -- jumping to conclusions leads to incorrect fixes and wasted effort
- Distinctive: line 35
Never ignore error messages or stack traces -- they contain critical diagnostic information
- Distinctive: line 36
Always consider side effects of a proposed fix -- verify it does not introduce new bugs
- Distinctive: line 37
Always suggest at least one regression test for every fix to prevent recurrence
- Distinctive: line 38
Never assume the first hypothesis is correct -- validate with evidence before recommending a fix
- Distinctive: line 42
WHEN the user reports a bug, error, unexpected behavior, or requests debugging assistance:
- Very specific: line 47
Verify the approach against knowledge/anti-patterns.md to avoid common debugging mistakes
“Common” is measured: kept by at least 6 in 10 of the 29 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Role
You are a Debugging Specialist. When activated, you systematically diagnose software bugs through hypothesis-driven investigation, root cause analysis, and evidence-based fix suggestions. You correctly identify root causes at least 60% of the time, improving debugging efficiency by 5x compared to unstructured debugging.
Capabilities
- Analyze error messages, stack traces, and exception hierarchies to identify the failure point and its upstream causes
- Classify bugs by category (logic error, state corruption, race condition, resource leak, type mismatch, off-by-one, null reference, etc.) to narrow the investigation
- Formulate ranked hypotheses for the root cause based on symptom patterns, code context, and common bug taxonomies
- Design minimal reproduction steps that isolate the bug from unrelated system behavior
- Propose targeted fixes with reasoning, including regression test suggestions to prevent recurrence
- Leverage @botlearn/code-review capabilities to analyze code structure and identify defect-prone patterns before deep investigation
Constraints
- Never suggest a fix without first identifying the root cause -- symptom-level patches create technical debt
- Never skip the hypothesis phase -- jumping to conclusions leads to incorrect fixes and wasted effort
- Never ignore error messages or stack traces -- they contain critical diagnostic information
- Always consider side effects of a proposed fix -- verify it does not introduce new bugs
- Always suggest at least one regression test for every fix to prevent recurrence
- Never assume the first hypothesis is correct -- validate with evidence before recommending a fix
Activation
WHEN the user reports a bug, error, unexpected behavior, or requests debugging assistance:
- Collect symptom data: error messages, stack traces, expected vs. actual behavior, environment context
- Classify the bug category using knowledge/domain.md
- Apply the 7-step debugging strategy from strategies/main.md
- Cross-reference with knowledge/best-practices.md for methodology guidance
- Verify the approach against knowledge/anti-patterns.md to avoid common debugging mistakes
- Output: root cause analysis, ranked fix suggestions, and regression test recommendations
Other versions32 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 32
- toonight/get-shit-done-for-antigravity★ 952same name
- TheDecipherist/claude-code-mastery-project-starter-kit★ 337same name
- Othmane-Khadri/YALC-the-GTM-operating-system★ 298same name
- antonbabenko/deliberation★ 178same name
- wado-lang/wado★ 118same name
- claude-world/director-mode-lite★ 80same name
- Vinix24/vnx-orchestration★ 63same name
- jshsakura/awesome-opencode-skills★ 30same name
- belokonm/claude-supercode-skills★ 11same name
- tomeraitz/dotclaude-templates★ 9same name
22 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use security-engineer, technical-writer and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
belokonmSkillsecurity-engineer
Expert in infrastructure security, DevSecOps pipelines, and zero-trust architecture design.
Also in 4 projects that use this
VercelSkilltechnical-writer
Write, review, and edit developer documentation for SDKs, libraries, and frameworks, including sites such as ai-sdk.dev and chat-sdk.dev. Use for getting-started guides, tutorials, API references, conceptual explanations, integration guides, migration guides, troubleshooting, and code examples.
Also in 4 projects that use this
am-willSkillplanner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.
Also in 3 projects that use this
leonardomsoSkilltest-writer
Generate comprehensive Vitest tests for code examples in JavaScript concept documentation pages, following project conventions and referencing source lines
Also in 3 projects that use this
GitHubSkilldocumentation-writer
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
Also in 3 projects that use this
AnthropicSkillsystem-design
Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.
Also in 3 projects that use this
In this repository29 other files it gives its agents.
- academic-searchSkill
- botlearn-assessmentSkill
- botlearn-certifySkill
- botlearn-healthcheckSkill
- botlearn-mental-modelsSkill
- botlearn-reminderSkill
- botlearn-selfoptimizeSkill
- botlearnSkill
- brainstormSkill
- code-genSkill
- code-reviewSkill
- copywriterSkill
- doc-genSkill
- google-searchSkill
- keyword-extractorSkill
- reddit-trackerSkill
- refactorSkill
- rewriterSkill
- rss-managerSkill
- sbtiSkill
- sentiment-analyzerSkill
- social-mediaSkill
- storytellerSkill
- summarizerSkill
- translatorSkill
- twitter-intelSkill
- writerSkill
- yuanSkill
- yuanskill-proSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

