Agent skill

Fix Bug

by danielvm-git in danielvm-git/bigpowers

Bug fix orchestrator — activeflow fixbug; reads specs/bugs/BUG-.md; chains investigate-bug, develop-tdd, validate-fix.

MITAuto-check passedDevelopment

Install Fix Bug

skills CLI
$ npx skills add danielvm-git/bigpowers --skill fix-bug -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install danielvm-git/bigpowers fix-bug --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/fix-bug .claude/skills/fix-bug && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
fix-bug
GitHub stars
256
Token cost
~690 tokens
SKILL.md length
295 words
Files
1
Skills in repo
39
Repo updated
First seen
Licence
MIT

At a glance

Bug fix orchestrator — activeflow fixbug; reads specs/bugs/BUG-.md; chains investigate-bug, develop-tdd, validate-fix.

  • Works in 5 steps: Step 1 — investigate-bug: If no… → Step 2 — diagnose-root: Run 4-phase RCA… → Step 3 — develop-tdd: develop-tdd… → …
  • User reports a defect
  • SKILL.md covers Discovered gate failures…, Five steps (bug_cycle in…, Process and Bug file SoT, plus 1 more section
  • Calls bash

What it does

Fix Bug is an agent skill from danielvm-git/bigpowers. Bug fix orchestrator — activeflow fixbug; reads specs/bugs/BUG-.md; chains investigate-bug, develop-tdd, validate-fix. Use when user reports a defect.

Its SKILL.md is about 690 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Debugging. The repository describes itself as: Agent skills synthesizing years of software engineering discipline into a prescriptive methodology for solo developers. The licence is MIT.

When your agent uses it

  • User reports a defect
  • Tasks that involve Debugging

Example prompts

  • “/fix-bug”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Step 1 — investigate-bug: If no specs/bugs/BUG-*.md, run investigate-bug first — it handles history check, RCA (via diagnose-root), fix…
  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.

What it can do on your machine

Read from SKILL.md and the folder at commit 812d57a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Fix Bug loads about 690 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 295 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~40
When it runs · the whole SKILL.md, loaded when a task matches
~690

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from danielvm-git/bigpowers at commit 812d57a, republished under its MIT licence (© danielvm-git). 295 words, ~690 tokens.

Download SKILL.mdSave it as .claude/skills/fix-bug/SKILL.md (or your agent's skills folder).
name
fix-bug
description
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.
model
sonnet
effort
standard

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

© danielvm-git, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/fix-bug of danielvm-git/bigpowers.

Open the folder on GitHubat commit 812d57a

Compare with similar skills

Fix Bug next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Fix Bug compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fix Bug this skilldanielvm-git/bigpowers256—~690Automated safety check: PassMIT
Trellis Session Insightmindfold-ai/Trellis15k4 repos~1.7kAutomated safety check: PassAGPL-3.0
Native Data FetchingCherryHQ/cherry-studio-app4k6 repos~2.9kAutomated safety check: NotesMIT
Aoti Debugpytorch/pytorch104k1 repos~1.7kAutomated safety check: PassCustom licence
Herdr Throwaway Reproductionherdrdev/herdr43k—~2.4kAutomated safety check: PassApache-2.0
Systematic Debuggingultralisp/ultralisp25851 repos~2.4kAutomated safety check: PassNone

Similar skills

  • Trellis Session Insight

    mindfold-ai/Trellis

    Reach into past AI conversation history through the trellis mem CLI.

    15k GitHub starsUsed in 4 repos~1.7k tokens
    DevelopmentAuto-check passed
  • Native Data Fetching

    CherryHQ/cherry-studio-app

    A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.

    4k GitHub starsUsed in 6 repos~2.9k tokens
    DevelopmentAuto-check: notes
  • Aoti Debug

    pytorch/pytorch

    Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.

    104k GitHub starsUsed in 1 repo~1.7k tokens
    DevelopmentAuto-check passed
  • Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.

    43k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Systematic Debugging

    ultralisp/ultralisp

    A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    258 GitHub starsUsed in 51 repos~2.4k tokens
    DevelopmentAuto-check passed
  • Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated 4 days ago
    DevelopmentAuto-check: notes

More from danielvm-git/bigpowers

All 39 skills in this repo
  • Extract Design

    danielvm-git/bigpowers

    Extract a Google DESIGN.md file from an HTML prototype (claude.ai/design or any styled page) using Puppeteer, producing machine-readable tokens and AI-generated prose.

    256 GitHub stars~1k tokensUpdated 16 days ago
    Auto-check passed
  • Align Grid

    danielvm-git/bigpowers

    Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one.

    256 GitHub stars~3k tokensUpdated 16 days ago
    Auto-check passed
  • Assess Impact

    danielvm-git/bigpowers

    Analyze the blast radius of a proposed change before any code is written.

    256 GitHub stars~766 tokensUpdated 16 days ago
    Auto-check passed
  • Audit Code

    danielvm-git/bigpowers

    Self-review checklist for the coding agent to run before dispatching a reviewer.

    256 GitHub stars~1.6k tokensUpdated 16 days ago
    Auto-check: notes
  • Audit Plan

    danielvm-git/bigpowers

    Evaluate an incoming project plan against bigpowers principles and conventions, surface gaps, and produce a READY/NOT READY verdict before engagement begins.

    256 GitHub stars~880 tokensUpdated 16 days ago
    Auto-check passed
  • Compose Workflow

    danielvm-git/bigpowers

    Chain multiple bigpowers skills into a custom workflow recipe saved in specs/.

    256 GitHub stars~723 tokensUpdated 16 days ago
    Auto-check passed

Categories

Questions about Fix Bug

What does Fix Bug do?

Bug fix orchestrator — activeflow fixbug; reads specs/bugs/BUG-.md; chains investigate-bug, develop-tdd, validate-fix. Fix Bug is an agent skill from danielvm-git/bigpowers.md; chains investigate-bug, develop-tdd, validate-fix.

When should I use Fix Bug?

Fix Bug fits situations like: user reports a defect; tasks that involve Debugging.

How do I install Fix Bug in Claude Code?

Run `npx skills add danielvm-git/bigpowers --skill fix-bug -a claude-code`. Or copy the skill folder (skills/fix-bug in danielvm-git/bigpowers) into .claude/skills/fix-bug in your project. Claude Code loads it when a task matches its description.

How do I install Fix Bug in Codex?

Run `npx skills add danielvm-git/bigpowers --skill fix-bug -a codex`. Or copy the skill folder (skills/fix-bug in danielvm-git/bigpowers) into .agents/skills/fix-bug in your project. Codex loads it when a task matches its description.

Can I use Fix Bug in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add danielvm-git/bigpowers --skill fix-bug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fix-bug, .gemini/skills/fix-bug, .github/skills/fix-bug and .opencode/skills/fix-bug in your project.

What does Fix Bug need to run?

Going by SKILL.md and its folder, Fix Bug needs the command-line tools its instructions call (bash).

Does Fix Bug access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Fix Bug safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Fix Bug use?

Fix Bug is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fix Bug use?

About 690 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Fix Bug?

Skills that share tags, products or a category with Fix Bug: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Aoti Debug (pytorch/pytorch, 104k stars) and Herdr Throwaway Reproduction (herdrdev/herdr, 43k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fix Bug?

danielvm-git (a GitHub user) maintains it in danielvm-git/bigpowers, which has 256 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on September 21, 2026.

Source: danielvm-git/bigpowers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.