Best use case
debug is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Systematic debugging workflow for bugs and test failures
Teams using debug should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/debug/SKILL.md --create-dirs "https://raw.githubusercontent.com/hivellm/rulebook/main/.claude/skills/debug/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/debug/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How debug Compares
| Feature / Agent | debug | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Systematic debugging workflow for bugs and test failures
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Debug the following issue: $ARGUMENTS Steps: 1. Reproduce the issue by reading the error message or running the failing test 2. Read the relevant source code and trace the execution path 3. Form a hypothesis about the root cause 4. Search for similar patterns in the codebase that work correctly 5. Identify the exact root cause with file and line reference 6. Propose a minimal fix with explanation
Related Skills
We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.