Help us improve
Share bugs, ideas, or general feedback.
From cc-best
Fixes GitHub issues end-to-end: analyzes issue, locates code, implements fixes with tests, verifies changes, commits, and closes. Supports [#issue-number] [--no-close] and multiples.
npx claudepluginhub xiaobei930/cc-best --plugin cc-bestHow this command is triggered — by the user, by Claude, or both
Slash command
/cc-best:fix-issue [#issue-number] [--no-close]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /fix-issue - Issue 修复闭环 从 GitHub Issue 出发,端到端完成修复闭环。**核心能力是自动化 Issue 分析→代码修复→测试验证→提交→关闭的完整流程。** > **Agent 集成**: > > - 代码定位使用 `exploration` 技能(Explore Agent) > - 修复实现调用 `tdd-guide` Agent 确保测试覆盖 > - 提交前调用 `/cc-best:verify` 综合验证 ## 使用方式 --- ## 执行流程 ### 第 0 步:守卫检查 - 确认 `gh` CLI 已安装且已认证 - 确认当前 `git status` 干净(无未提交变更) - 确认 Issue 存在且状态为 Open ### 第 1 步:读取 Issue - 提取 Issue 标题、描述、标签 - 分析 Issue 类型:`bug` / `feature` / `enhancement` / `question` - 读取评论中的补充信息 ### 第 2 步:分析与定位 - 根据 Issue 描述使用 `exploration` 技能定位相关代码 - 建立 TodoWrite 任务清单,列出需要修改的文件 - 如果 Issue 涉及多个模块,按依赖关系排序 ### 第 3 步:实施修复 - ...
/fix-github-issueAnalyzes GitHub issue by number, implements fixes, adds/runs tests, verifies linting/type checks, and creates commit.
/fix-github-issueFixes a GitHub issue by fetching details, analyzing code, implementing solution with tests, verifying changes, and creating a pull request.
/fix-issueFetches GitHub issue by number using gh CLI, analyzes it, implements code fix, verifies changes, and summarizes edits without committing.
/github-issue-fixAnalyzes GitHub issue via gh CLI, identifies sub-issues/dependencies, breaks into tasks, and documents structured fix plan in scratchpad.
/fix-issueFixes GitHub issue by number: fetches details with gh CLI, creates feature branch, implements minimal fix with tests, commits, and opens PR.
/fix-issueFixes GitHub issues by analyzing repo context with given issue number, implementing solution, testing changes, and validating integration.
Share bugs, ideas, or general feedback.
从 GitHub Issue 出发,端到端完成修复闭环。核心能力是自动化 Issue 分析→代码修复→测试验证→提交→关闭的完整流程。
Agent 集成:
- 代码定位使用
exploration技能(Explore Agent)- 修复实现调用
tdd-guideAgent 确保测试覆盖- 提交前调用
/cc-best:verify综合验证
# 修复指定 Issue
/cc-best:fix-issue #123
# 修复 Issue 并跳过关闭(仅提交代码)
/cc-best:fix-issue #123 --no-close
# 批量修复多个 Issue
/cc-best:fix-issue #123 #124 #125
gh CLI 已安装且已认证git status 干净(无未提交变更)gh issue view <NUMBER> --json title,body,labels,assignees,comments
bug / feature / enhancement / questionexploration 技能定位相关代码tdd-guide Agent)关键原则: 最小化修改范围,不做超出 Issue 描述的额外变更
调用 /cc-best:verify 执行综合验证:
调用 /cc-best:commit 生成规范的提交信息:
fix: <简要描述> (#<ISSUE_NUMBER>)feat: 前缀Closes #<NUMBER>gh issue close <NUMBER> --comment "修复已提交: <commit-sha>\n\n变更摘要:\n- <变更列表>"
--no-close,仅评论不关闭| 场景 | 处理方式 |
|---|---|
| Issue 不存在 | 报错退出,提示检查 Issue 编号 |
| gh 未认证 | 提示执行 gh auth login |
| 测试失败 | 继续修复,不跳过测试 |
| 构建失败 | 调用 build-error-resolver Agent 分析 |
| 修改范围过大 | 提醒用户拆分 Issue |
| 命令 | 关系 |
|---|---|
/cc-best:verify | 第 4 步调用,综合验证 |
/cc-best:commit | 第 5 步调用,规范提交 |
/cc-best:dev | 类似但更通用,fix-issue 专注 Issue 闭环 |
/cc-best:iterate | 可在 iterate 模式中自动调用 fix-issue |
记住: Issue 修复要端到端——从复现到测试到提交,缺少任何一环都不算完成。