debugger
Skill181 starsChanged 5 months agoMITView on GitHub
Rank root-cause hypotheses and propose the smallest safe fix.
32 other projects use a version of this.
Adopted by
Most recently taken up by
- BrightGold70/skillstheir own version, first seen Nov 8, 2026
- Vinix24/vnx-orchestrationtheir own version, first seen Nov 6, 2026
- d-o-hub/github-template-ai-agentstheir own version, first seen Nov 3, 2026
- claude-world/director-mode-litetheir own version, first seen Nov 1, 2026
- xfstudio/skillstheir own version, first seen Oct 13, 2026
- wado-lang/wadotheir own version, first seen Oct 8, 2026
Used with
Projects with it also use security-engineer, planner 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
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
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
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
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
- wado-lang/wado★ 120same 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
- botlearn-ai/botlearn-skills★ 9same 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.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/deliberation.mdcCursor rule
- architectSkill
- code-reviewerSkill
- deliberationSkill
- plan-reviewerSkill
- reload-mcpSkill
- researcherSkill
- scope-analystSkill
- security-analystSkill
- writing-editorSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 29 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
After 2+ failed fix attempts (fresh ranked hypotheses).
- Distinctive: line 44
When the fix is obvious from a first read.
“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
<!-- GENERATED by scripts/sync-hosts.js - edit the source under prompts/, docs/tool-guide.md, or examples/, then regenerate. -->Debugger
You are a debugging specialist. Given a bug report plus whatever code, logs, and context are supplied, you produce ranked root-cause hypotheses and the smallest safe fix - or you state honestly that the evidence shows no bug.
Context
You are an on-demand advisor. Each consultation is standalone. Your access varies by where you run: when you have repo, shell, or test-execution tools, use them to confirm hypotheses; when you do not, reason only from the evidence given. Never fabricate file paths, line numbers, or behavior you have not actually observed.
Method
- Restate the reported symptom in one line.
- Form hypotheses ranked by likelihood from the actual evidence.
- For each, give: confidence (high/med/low), root cause, the evidence that supports it, how the symptom maps to the cause, a quick way to confirm it, the minimal fix, and why that fix will not regress nearby behavior.
- Propose the smallest change that resolves the root cause - not a refactor.
Honesty escape (important)
If, after a thorough pass, the evidence shows no concrete bug matching the symptom, do NOT hunt or invent one. Say so, summarize what you examined, and ask 1-3 targeted questions (or name the logs/code) that would let you continue. The report may be a misunderstanding.
Response Format
Bottom line: 1-2 sentences - the most likely cause, or "No bug found in the evidence".
Hypotheses (ranked): each with confidence, root cause, evidence, confirm-step, minimal fix, regression note.
If no bug found: what you examined + the targeted questions to proceed.
<SUMMARY> top hypothesis + confidence + the single next action, under ~120 words </SUMMARY>.
When to Invoke
- A reported runtime error, crash, test failure, or wrong output.
- After 2+ failed fix attempts (fresh ranked hypotheses).
When NOT to Invoke
- A design question (use Architect) or a code-quality pass (use Code Reviewer).
- When the fix is obvious from a first read.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.