Debugger
Systematic issue diagnosis skill that isolates root causes, tests hypotheses, and produces minimal fix strategies
- License 许可
- MIT
- 最近更新
- 2026-06-22
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- Debugger
- tags
- [ "debugging", "diagnosis", "troubleshooting" ]
- author
- ForgeWeave Core
- version
- 1.0.0
- skill_id
- debugger
- description
- Systematic issue diagnosis skill that isolates root causes, tests hypotheses, and produces minimal fix strategies
- tui_compatibility
- [ "opencode", "claude", "gemini", "qwen" ]
02 资源文件 2
- 参考文档references/debugging-methodology.md1.5 KB
- 脚本scripts/hypothesis_tracker.py2.4 KB
03 SKILL.md 正文
Debugger
Purpose
Apply systematic debugging methodology to identify root causes of software issues. Uses hypothesis-driven investigation, binary search on code paths, and targeted tests to isolate the problem before proposing a fix.
When to Use
- The user reports a bug, error, or unexpected behavior
- A test is failing and the cause is not obvious
- A feature works locally but fails in production
- Performance regression needs investigation
When Not to Use
- The error message is self-explanatory — fix it directly
- The fix is already known and just needs implementation
- The task is refactoring — use
refactor-engine
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
symptom |
string | Yes | The observed error or unexpected behavior |
reproduction_steps |
string | No | Steps to reproduce the issue |
environment |
string | No | Environment details (OS, versions, deployment) |
logs_or_stacktrace |
string | No | Error output, logs, or stack trace |
Expected Outputs
| Output | Description |
|---|---|
| Root cause | Identified source of the issue |
| Fix strategy | Minimal change to fix the issue |
| Verification steps | How to confirm the fix works |
| Prevention | How to avoid similar issues |
Exact Workflow Steps
- Understand the symptom and reproduction steps
- Formulate 2-3 hypotheses for root cause
- For each hypothesis, design a diagnostic test
- Narrow down by eliminating hypotheses
- Isolate the exact root cause
- Design minimal fix that doesn't break other functionality
- Verify fix resolves the symptom
- Run existing tests to confirm no regressions
Required Checks
- [ ] Root cause is identified before any fix is proposed
- [ ] Fix is minimal (no scope creep)
- [ ] Existing tests pass after fix
- [ ] Prevention strategy is documented
Failure Modes
| Failure Condition | Response |
|---|---|
| Cannot reproduce the issue | Ask for more detailed reproduction steps |
| All hypotheses eliminated | Broaden search to adjacent systems or dependencies |
| Fix breaks other functionality | Revert and explore alternative fix strategy |
Examples
Example: "API returns 500 intermittently"
- Hypotheses: database connection pool exhaustion, unhandled exception, timeout
- Check connection pool metrics → pool is fine
- Add error logging around the failing endpoint → caught unhandled promise rejection
- Fix: wrap async handler in try/catch
References
| Reference | Path |
|---|---|
| Test Generator skill | ../test-generator/SKILL.md |
04 同仓库更多 Skills
Workflow Orchestrator
Coordinates multi-skill execution pipelines (e.g., research → plan → build → test)
Web Research
Browser-driven or scraping-based skill for real-time internet extraction using Playwright and HTTP-based fetching
Validation Engine
Checks outputs from other skills for consistency, correctness, and adherence to AGENTS.md rules
Tool Selector
Determines which tools, APIs, MCP actions, or system capabilities are required for a given task
Test Generator
Creates test plans and test cases (unit, integration, edge cases) based on existing or planned code
Skill Generator
Meta-skill that creates new SKILL.md files from research outputs and patterns discovered in execution