New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Bug Fixer

by hex in hex/claude-council

A bug reproduces, the expected behaviour is clear, and the fix stands apart from the current work.

MITAuto-check passedAgent Workflows

Install Bug Fixer

skills CLI
$ npx skills add hex/claude-council --skill bug-fixer -a claude-code

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

GitHub CLI
$ gh skill install hex/claude-council bug-fixer --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/hex/claude-council.git skills-src && mkdir -p .claude/skills && cp -r skills-src/mods/council-pane/specialists/bug-fixer .claude/skills/bug-fixer && 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
bug-fixer
GitHub stars
851
Token cost
~991 tokens
SKILL.md length
648 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

A bug reproduces, the expected behaviour is clear, and the fix stands apart from the current work.

  • Works in 3 steps: Restate the bug in one sentence: what… → Read the project's own instructions… → Reproduce the failure. Prefer the real…
  • Agent Workflows work in your project
  • SKILL.md covers Before you change anything, Find the cause, Make the fix and Prove it, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Bug Fixer is an agent skill from hex/claude-council. A bug reproduces, the expected behaviour is clear, and the fix stands apart from the current work.

Its SKILL.md is about 990 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 Agent Workflows. The repository describes itself as: Claude Code plugin that asks several AI coding agents the same question and shows their answers side by side. Gemini, OpenAI, Grok, Perplexity, Kimi and any model OpenRouter… The licence is MIT.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/bug-fixer”

Workflow steps

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

  1. Restate the bug in one sentence: what the user does, what happens, what
  2. Read the project's own instructions (AGENTS.md, CONTRIBUTING, README) for
  3. Reproduce the failure. Prefer the real user path: the command, request or

What it can do on your machine

Read from SKILL.md and the folder at commit b84ff69. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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

Bug Fixer loads about 991 tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 648 words of instructions outside code blocks.

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

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 hex/claude-council at commit b84ff69, republished under its MIT licence (© hex). 648 words, ~991 tokens.

Download SKILL.mdSave it as .claude/skills/bug-fixer/SKILL.md (or your agent's skills folder).
name
bug-fixer
description
A bug reproduces, the expected behaviour is clear, and the fix stands apart from the current work.

Bug Fixer

Fix one reported bug at its root cause, with proof that the fix works. The change must be as small as it can be. Every claim in your report must rest on something you ran.

Before you change anything

  1. Restate the bug in one sentence: what the user does, what happens, what should happen. If the task does not say what should happen, and neither a spec, the docs, nor an existing test settles it, stop and report the ambiguity instead of choosing.
  2. Read the project's own instructions (AGENTS.md, CONTRIBUTING, README) for how to build and run tests.
  3. Reproduce the failure. Prefer the real user path: the command, request or UI action from the report. Record the exact command and the output that shows the bug. If it does not reproduce, stop and report what you tried and what you saw. Do not fix a bug you cannot see.

Find the cause

  • Trace from the symptom to the code that makes the wrong decision. Read the owning function, its callers and callees, and any sibling implementation that does the same job correctly. Diff the two.
  • State one hypothesis and test it with the smallest check that can prove it wrong: a log line, a debugger stop, a narrowed input. If it is wrong, go back and re-read; do not stack guesses.
  • Distinguish cause from symptom. A null check where the value arrives is a symptom patch if the real fault is the code that should never have produced the null.

Make the fix

  • Change the code that owns the decision, not a caller that happens to see the bad result.
  • Keep the diff minimal. No refactors, renames, formatting sweeps or unrelated cleanups. Note them in the report instead.
  • No fallback that hides the failure: no silent default, no swallowed exception, no retry that masks the cause. If the bad state is impossible after the fix, fail loudly if it appears anyway.
  • Never weaken, skip or delete a test to get a pass. A failing test is information. If a test encodes the buggy behaviour as expected, say so in the report with the evidence, and change it only when the spec proves it wrong.
Show full SKILL.md (279 more words)Show less

Prove it

  1. Run the reproduction again. It must now show the expected behaviour.
  2. If the repo has a test at the boundary that owns the behaviour and no existing test caught this bug, add one there. It must fail on the pre-fix code for the intended reason and pass after the fix. Show both runs: undo the fix, run it, restore the fix, run it again. A test you never saw fail proves nothing. If an existing test already covers the behaviour and only missed this input, extend that test instead of adding a new one named after the bug.
  3. Run the tests for the touched module and its nearest neighbours. Report any failure, including ones you believe pre-date your change, with the output.

Evidence to record

  • Reproduction command and the output before and after the fix.
  • Root cause: the file, the function, and why it produced the wrong result.
  • The test added or extended, with the failing run (pre-fix) and the passing run.
  • Other test commands run and their results.

Stop conditions

Stop and report without further changes when:

  • the bug does not reproduce;
  • the expected behaviour is disputed or unspecified;
  • the root cause is in a dependency, generated code or infrastructure you should not edit;
  • the correct fix needs a design change larger than a bug fix.

Handoff

Report, in this order:

  1. Outcome: fixed, not reproduced, or blocked.
  2. Root cause, in two or three sentences.
  3. The change: files touched and why.
  4. Proof: the commands above with their results.
  5. Anything left: related bugs seen, cleanups skipped, open questions.

Regression-test rule adapted from openclaw's test-audit skill (MIT, OpenClaw Foundation); see ../LICENSE-openclaw.

© hex, 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 mods/council-pane/specialists/bug-fixer of hex/claude-council.

Open the folder on GitHubat commit b84ff69

Compare with similar skills

Bug Fixer 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.

Bug Fixer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bug Fixer this skillhex/claude-council851—~991Automated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79589 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes

  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed

  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from hex/claude-council

All 10 skills in this repo

  • Local Council Execution

    hex/claude-council

    Runs a local council when no external AI providers are configured.

    851 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Council Execution

    hex/claude-council

    Executes council queries by running the query pipeline across selected AI providers (Gemini, OpenAI, Grok, Perplexity), displaying formatted responses verbatim, and generating a synthesis of…

    851 GitHub stars~824 tokensUpdated today
    Auto-check passed

  • Deep Execution

    hex/claude-council

    Executes agent-enhanced council queries as one Workflow of parallel Claude analyst agents that each query a provider, evaluate response quality, ask follow-up questions, and return a schema-enforced…

    851 GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Provider Integration

    hex/claude-council

    Adds new AI providers to claude-council, configures provider API settings, troubleshoots provider connections, and documents the provider script interface.

    851 GitHub stars~635 tokensUpdated today
    Auto-check passed

  • CI Fixer

    hex/claude-council

    A CI job fails on a named revision and the fix belongs in code, config or tests, not in the CI provider.

    851 GitHub stars~941 tokensUpdated today
    Auto-check passed

  • Docs Updater

    hex/claude-council

    Docs must be updated or restructured to match code that already changed: README, reference pages, CLI help or config docs.

    851 GitHub stars~930 tokensUpdated today
    Auto-check passed

Categories

Questions about Bug Fixer

What does Bug Fixer do?

A bug reproduces, the expected behaviour is clear, and the fix stands apart from the current work. Bug Fixer is an agent skill from hex/claude-council. A bug reproduces, the expected behaviour is clear, and the fix stands apart from the current work.

When should I use Bug Fixer?

Bug Fixer fits situations like: agent Workflows work in your project.

How do I install Bug Fixer in Claude Code?

Run `npx skills add hex/claude-council --skill bug-fixer -a claude-code`. Or copy the skill folder (mods/council-pane/specialists/bug-fixer in hex/claude-council) into .claude/skills/bug-fixer in your project. Claude Code loads it when a task matches its description.

How do I install Bug Fixer in Codex?

Run `npx skills add hex/claude-council --skill bug-fixer -a codex`. Or copy the skill folder (mods/council-pane/specialists/bug-fixer in hex/claude-council) into .agents/skills/bug-fixer in your project. Codex loads it when a task matches its description.

Can I use Bug Fixer 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 hex/claude-council --skill bug-fixer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bug-fixer, .gemini/skills/bug-fixer, .github/skills/bug-fixer and .opencode/skills/bug-fixer in your project.

What does Bug Fixer need to run?

SKILL.md names no scripts, command-line tools or credentials: Bug Fixer is instructions for the agent only.

Does Bug Fixer 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 Bug Fixer 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 Bug Fixer use?

Bug Fixer 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 Bug Fixer use?

About 991 tokens (SKILL.md is roughly 4k 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 Bug Fixer?

Skills that share tags, products or a category with Bug Fixer: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bug Fixer?

hex (a GitHub user) maintains it in hex/claude-council, which has 851 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 8, 2026.

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