Fix Bug logo

Fix Bug

Community
danielvm-git
fix-bug

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.

Overview

Publisherdanielvm-git
Repositorybigpowers
Skill namefix-bug
Stars
206
Forks
18
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by danielvm-git on GitHub. Read the source before you install it.

Installation

Install the Fix Bug AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/danielvm-git/bigpowers.git /tmp/bigpowers
mkdir -p .claude/skills
cp -r /tmp/bigpowers/skills/fix-bug .claude/skills/fix-bug
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Fix Bug in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Fix Bug on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Fix Bug is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Fix Bug

Boundary: Orchestrator flow — chains investigate-bug (entry point + RCA via diagnose-root) → develop-tddvalidate-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

Frequently asked questions

What does the Fix Bug AI skill do?

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.

Why use Fix Bug on TypingMind?

Because you install it once and use it with any model. Fix Bug is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Fix Bug in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/danielvm-git/bigpowers/tree/main/skills/fix-bug. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Fix Bug?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Fix Bug?

As many as you like. As long as a model supports skills, you can use Fix Bug with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Fix Bug AI skill free?

Yes. It is published on GitHub by danielvm-git under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇