bug-investigator
Use when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes. Invoked automatically when build-executor hits a blockage.
npx skills add MageByte-Zero/spec-superflow --skill bug-investigator --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.
# Bug Investigator **Core principle:** Find root cause before attempting fixes. Symptom fixes are failure. ## The Iron Law No fixes without root cause investigation first. If you haven't completed Phase 1, you cannot propose fixes. ## When to Use Use for ANY technical issue: test failures, bugs, unexpected behavior, performance problems, build failures, integration issues. Especially when under ti
What does the bug-investigator skill do?
Use when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes. Invoked automatically when build-executor hits a blockage.
How do I install it?
Run `npx skills add MageByte-Zero/spec-superflow --skill bug-investigator --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 MageByte-Zero/spec-superflow, a repository with 668 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.
