Babysitter systematic-debugging
Structured debugging methodology using hypothesis-driven investigation, log analysis, and bisection to isolate and resolve defects.
install
source · Clone the upstream repo
git clone https://github.com/a5c-ai/babysitter
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/a5c-ai/babysitter "$T" && mkdir -p ~/.claude/skills && cp -r "$T/library/methodologies/rpikit/skills/systematic-debugging" ~/.claude/skills/a5c-ai-babysitter-systematic-debugging && rm -rf "$T"
manifest:
library/methodologies/rpikit/skills/systematic-debugging/SKILL.mdsource content
Systematic Debugging
Overview
Structured approach to investigating and resolving defects using hypothesis-driven methodology rather than trial-and-error.
When to Use
- Step verification fails during implementation
- Unexpected behavior discovered during testing
- Bug reports require investigation
- Performance issues need root cause analysis
Process
- Reproduce - Confirm the defect with a minimal reproduction
- Hypothesize - Form theories about the root cause
- Investigate - Systematically test hypotheses (logs, breakpoints, bisection)
- Isolate - Narrow to the specific component/line
- Fix - Apply targeted fix addressing root cause
- Verify - Confirm fix resolves the issue without regression
Key Rules
- Never apply fixes without understanding the root cause
- Use web-researcher agent for unfamiliar error patterns
- Document the investigation path for future reference
- Verify that the fix does not introduce regressions
Tool Use
Integrated into
methodologies/rpikit/rpikit-implement