bug-fix — Claude Code plugin: what it does, how to install
bug-fix — a Claude Code plugin that opens a GitHub issue for a bug, branches off to fix it, and tests the change before it merges.
no license ★ 2,003 updated 2026-07-26
/plugin marketplace add composio-community/awesome-claude-plugins
/plugin install bug-fix@awesome-claude-pluginsWhat bug-fix does
bug-fix takes a bug in your codebase, analyzes it, and works toward a fix in a set order. It starts by filing an issue on GitHub. Then it moves to a feature branch, where the change is written and run against tests. Merging comes last.
Every fix ends up tied to its own issue and branch, so the history of a bug is easy to follow. The issue step happens on GitHub, which means your project needs to be hosted there.
The plugin is listed in the composio-community/awesome-claude-plugins marketplace under the author name Community.
What it helps with
- Track down the cause of a bug in existing code
- File a GitHub issue for an error you just found
- Keep a fix on its own feature branch
- Run tests on a change before merging it
Example prompts for the agent
- Use the bug-fix plugin to fix the crash when the cart is empty
- Run bug-fix on the broken date parser: open an issue first, then fix it on a branch
- Find the cause of the payment handler error with bug-fix and test the change
How to install bug-fix
Plugin marketplace
/plugin marketplace add composio-community/awesome-claude-plugins/plugin install bug-fix@awesome-claude-pluginsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about bug-fix
How do I install bug-fix in Claude Code?
Run two commands in order: /plugin marketplace add composio-community/awesome-claude-plugins, then /plugin install bug-fix@awesome-claude-plugins.
What does bug-fix do?
It analyzes a bug in your codebase and fixes it. Along the way it creates a GitHub issue and a separate branch for the change.
What happens to a fix before it is merged?
The change is written on a branch created after the issue, and it goes through testing. Only then does the merge happen.