danielvm-git/bigpowers/fix-bug

Claude Code and agent skill by danielvm-git/bigpowers

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Bug fix orchestrator — active_flow fix_bug; reads specs/bugs/BUG-*.md; chains investigate-bug, develop-tdd, validate-fix. Use when user reports a defect.

Install

npx vskill@latest install danielvm-git/bigpowers/fix-bug

SKILL.md

Fix Bug

Boundary: Orchestrator flow — chains investigate-bug (entry point + RCA via diagnose-root) → develop-tdd → validate-fix. Does not implement RCA or write bug files directly.

Orchestrates fix_bug flow without mixing epic build state.

HARD GATE — Set specs/state.yaml active_flow: fix_bug and bug_cycle.current_step: 1 before starting.

Discovered gate failures (e51s04)

Valid entry without a user-reported bug when:

  • Preflight or CI is red at kickoff or verify-work
  • Golden suite or project baseline is red (bash scripts/run-verification-gates.sh or equivalent)
  • A reproducible gate failure during unrelated epic work exceeds quick-fix guardrails

Create specs/bugs/BUG-*.md via investigate-bug (or inline in fix-bug step 1) describing the gate failure, then run the standard fix_bug chain.

Five steps (bug_cycle in state.yaml)

StepSkill / action
1investigate-bug — create BUG-*.md with RCA
2diagnose-root — 4-phase root cause analysis
3develop-tdd — red-green against bug file verify steps
4validate-fix — re-run failing test, full suite, lint
5release-branch — PR or solo land the fix
Checkpoint / resume

Track progress via specs/state.yaml bug_cycle:

  • bug_cycle.current_step: current step (1–5)
  • bug_cycle.completed_steps: completed step numbers
  • handoff.next_skill: skill for the current step
  • On resume, read bug_cycle.current_step and continue from there

Process

  1. Step 1 — investigate-bug: If no specs/bugs/BUG-*.md, run investigate-bug first — it handles history check, RCA (via diagnose-root), fix approach, and writes the bug file. Increment bug_cycle.current_step to 2 on completion.
  2. Step 2 — diagnose-root: Run 4-phase RCA (reproduce → isolate → hypothesize → verify). Record findings in the bug file. Increment to step 3.
  3. Step 3 — develop-tdd: develop-tdd against the bug file's verify steps. Increment to step 4 on all-green.
  4. Step 4 — validate-fix: validate-fix — re-run failing test, full suite, typecheck, lint. Increment to step 5.
  5. Step 5 — release-branch: Land the fix via release-branch. Clear bug_cycle and active_flow when done.

Bug file SoT

One markdown file per bug with frontmatter:

yaml
---
bug_id: BUG-001
status: open
severity: high
scope: api
title: Short title
---

Verify

→ verify: test -d specs/bugs && test -f scripts/run-skill-verify.sh

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

See the full security report

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

See evaluation results

Source

Popularity

Repository stars
188
Repository forks
18
7-day trend score
26

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/danielvm-git/bigpowers/fix-bug/badge)](https://verified-skill.com/skills/danielvm-git/bigpowers/fix-bug)

Something wrong with this skill or its page? Tell us.