Individual skill
debugger
Rank root-cause hypotheses and propose the smallest safe fix.
plugins/deliberation/skills/debugger/SKILL.md
Source commit 687bfe4d47cd2322940443ee92390d2b46de43b0
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 181
- Repository last updated
- Nov 4, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- code-review Repository topic
- codex Repository topic
- gemini Repository topic
- grok Repository topic
- llm Repository topic
- plan-review Repository topic
- security-review Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
<!-- 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
1. Restate the reported symptom in one line.
2. Form hypotheses ranked by likelihood from the actual evidence.
3. 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.