Bug 修复收尾。清理 worktree/分支与 .bugfix-flow/ 状态目录。支持 manual 和 auto 模式。
轻量 bug 修复编排器。通过 .bugfix-flow/ 状态机管理从问题接手到验证完成的修复流程, 支持 manual 和 auto 两种模式,默认在验证通过后暂停等待人工决定是否提交或创建 PR。
执行 bug 修复。读取 .bugfix-flow/context.json,围绕复现路径和验证目标做最小修改, 支持从 ready 重新进入修复循环。
接手一个 bug 修复任务:从 GitHub Issue 或自由文本构建修复上下文,创建隔离 worktree 和分支, 初始化 .bugfix-flow/。为后续修改和验证做准备。
Bug 修复验证器。运行聚焦测试与 lint,对照 .bugfix-flow/context.json 中的验证目标 检查修复是否成立,输出 verify-report。
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Issue-Flow is a workflow plugin for coding agents. It ships an issue-driven delivery orchestrator plus a lightweight bugfix repair flow so agents can either drive a feature from issue creation to review or take a bug from reproduction to verified fix.
Issue-Flow is built to work with superpowers. Superpowers provides the core development workflows, and Issue-Flow adds a lightweight state machine around them so agent sessions can stay aligned with a single issue from start to finish.
Issue-Flow ships two workflow state machines:
issue-flowThe issue-driven workflow has two parts: a pre-worktree phase that produces a GitHub Issue number, and a persistent state machine that tracks delivery from that point on.
Pre-worktree phase (short-lived pending state in the source repo):
issue-brainstorm turns a rough request into a design directionissue-create turns the design spec into a GitHub Issue number.issue-flow/pending.json can recover this short phase before a target worktree existsPersistent state machine (.issue-flow/ created by issue-pick):
picked -> researching -> planned -> implementing -> committing -> pring -> reviewing -> finished
Each persistent state maps to a focused skill:
issue-pick attaches the session to a specific issue and branch contextissue-research captures codebase findings before planningissue-plan creates an implementation planissue-implement carries out the planissue-verify checks tests, linting, and review feedbackissue-commit prepares clean commitsissue-pr opens the pull request and hands off into reviewissue-finish wraps up branch and workspace stateThe top-level issue-flow skill is the orchestrator. It reads the current session state and routes the agent to the next correct step.
bugfix-flowThe bugfix workflow is intentionally narrower. It is for cases where you already know there is a bug and want the agent to focus on reproducing, fixing, and verifying it before any commit or PR step.
Bugfix work usually goes directly to bugfix-pick. If it must pause before a worktree exists, .bugfix-flow/pending.json can hold that short-lived pending state in the source repo.
Persistent state machine (.bugfix-flow/ created by bugfix-pick):
picked -> implementing -> ready -> finished
Each persistent state maps to a focused skill:
bugfix-pick creates worktree/context from either a bug description or an existing issuebugfix-implement applies the minimal code changes needed for the fixbugfix-verify runs focused verification and loops back on failurebugfix-finish cleans up the bugfix session after the user decides to stopThe top-level bugfix-flow skill is the orchestrator. It routes the session until verification passes, then pauses in ready so a human can decide whether to commit or open a PR.
Issue-Flow currently supports Claude Code and Codex.
Issue-Flow depends on:
gitgh for GitHub issue and pull request operationsInstall superpowers first:
/plugin install superpowers@claude-plugins-official
Then add the Issue-Flow marketplace and install the plugin:
/plugin marketplace add crazygit/issue-flow
/plugin install issue-flow@issue-flow-marketplace
Restart Claude Code if the new plugin does not appear immediately.
Codex installation exposes issue-flow through either a personal marketplace or the repo marketplace, and the personal installer also enables the required plugins in user-level Codex config.
The Codex bundle entry point is .codex-plugin/plugin.json.
Recommended: personal marketplace
Run the installer from this repository:
bash scripts/install-codex.sh
The script will:
~/.codex/plugins/issue-flow~/.agents/plugins/marketplace.jsonissue-flow entry in your user-level marketplace config~/.codex/config.tomlsuperpowers@openai-curatedissue-flow@<your personal marketplace id>npx claudepluginhub crazygit/issue-flow --plugin issue-flowHarness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Feature development with code-architect/explorer/reviewer agents, CLAUDE.md audit and session learnings, and Agent Skills creation with eval benchmarking from Anthropic.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.