systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Requires root cause investigation first.
npx skills add a5c-ai/babysitter --skill systematic-debugging --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
## When 3+ Fixes Fail Stop and question the architecture. Pattern of repeated failures indicates architectural problems, not implementation bugs. ## Red Flags (STOP and Follow Process) - "Quick fix for now" - "Just try changing X" - Proposing solutions before tracing data flow - "One more fix attempt" (when already tried 2+) ## Agents Used - Process agents defined in `systematic-debugging.js` ## Tool Use Invoke via babysitter process: `methodologies/superpowers/systematic-debugging`
- When 3+ Fixes Fail
- Red Flags (STOP and Follow Process)
- Agents Used
- Tool Use
What does the systematic-debugging skill do?
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Requires root cause investigation first.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill systematic-debugging --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.