bug-blitz by arjenschwarz/agentic-coding
npx skills add https://github.com/arjenschwarz/agentic-coding --skill bug-blitz并行解决所有未解决的 bug —— 每个 bug 对应一个工作树和一个子代理。
首先,通过调用 mcp__transit__get_projects() 并匹配当前仓库名称与项目列表来确定当前项目。如果未找到匹配的 Transit 项目,则通知用户并停止。
然后查询 Transit 中所有状态为 "idea" 的 bug 类型任务,并按匹配的项目进行筛选:
mcp__transit__query_tasks(type="bug", status=["idea"], project="{project_name}")
如果未找到任何 bug,则通知用户并停止。
向用户展示 bug 列表,包括其 T-{displayId} 引用和名称。在继续之前请求确认。用户可以选择排除特定的 bug。
对于每个确认的 bug:
从任务名称派生出 kebab-case 格式的 bug 名称
基于 main 分支创建工作树,分支名为 T-{displayId}/bugfix-{bug-name}:
git worktree add ../{repo-name}-worktrees/T-{displayId} -b T-{displayId}/bugfix-{bug-name} main
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
所有工作树都放在同级目录 ../{repo-name}-worktrees/ 中,以保持主仓库的整洁。使用仓库的目录名作为 {repo-name}。
如果某个 bug 的工作树或分支已存在,则跳过创建并重用现有的。
使用 subagent_type="general-purpose" 为每个 bug 生成一个 Task 子代理。并行运行所有子代理(单条消息,多个 Task 工具调用)。
每个子代理接收以下提示(填入相应的值):
您正在 {worktree_path} 的 git 工作树中工作。
请修复 Transit 工单 T-{displayId} 描述的 bug:
- 名称:{task_name}
- 描述:{task_description}
使用工单引用 T-{displayId} 运行 /fix-bug 技能。
工作树已经检出了正确的分支 —— 请勿创建新分支或切换分支。
完全在 {worktree_path} 作为您的工作目录内工作。
重要提示:fix-bug 技能会将其 Transit 集成的一部分处理分支创建。由于工作树已有正确的分支,子代理的工作目录确保其在正确的位置操作。fix-bug 技能将检测到现有分支并跳过分支创建。
所有子代理完成后,在表格中总结结果:
| Bug | 分支 | 状态 | PR |
|---|---|---|---|
| T-{id}: {name} | T-{id}/bugfix-{name} | 成功/失败 | #{pr} 或 — |
报告完成后,提供删除工作树的选项:
git worktree remove ../{repo-name}-worktrees/T-{displayId}
仅删除已成功解决(PR 已创建)的 bug 对应的工作树。保留失败 bug 的工作树,以便用户进行调查。
每周安装次数
1
仓库
GitHub 星标数
16
首次出现
9 天前
安全审计
安装于
amp1
cline1
opencode1
cursor1
continue1
kimi-cli1
Resolve all open bugs in parallel — one worktree and one subagent per bug.
First, determine the current project by calling mcp__transit__get_projects() and matching the current repository name against the project list. If no matching Transit project is found, inform the user and stop.
Then query Transit for all bug-type tasks in "idea" status, filtered by the matched project:
mcp__transit__query_tasks(type="bug", status=["idea"], project="{project_name}")
If no bugs are found, inform the user and stop.
Present the list of bugs to the user with their T-{displayId} references and names. Ask for confirmation before proceeding. The user may choose to exclude specific bugs.
For each confirmed bug:
Derive a bug name in kebab-case from the task name
Create a worktree based off main with branch T-{displayId}/bugfix-{bug-name}:
git worktree add ../{repo-name}-worktrees/T-{displayId} -b T-{displayId}/bugfix-{bug-name} main
All worktrees go in a sibling directory ../{repo-name}-worktrees/ to keep the main repo clean. Use the repo's directory name as {repo-name}.
If a worktree or branch already exists for a bug, skip creation and reuse it.
Spawn one Task subagent per bug using subagent_type="general-purpose". Run all subagents in parallel (single message, multiple Task tool calls).
Each subagent receives this prompt (fill in the values):
You are working in a git worktree at {worktree_path}.
Fix the bug described by Transit ticket T-{displayId}:
- Name: {task_name}
- Description: {task_description}
Run the /fix-bug skill with the ticket reference T-{displayId}.
The worktree already has the correct branch checked out — do NOT create a new branch or switch branches.
Work entirely within {worktree_path} as your working directory.
Important: The fix-bug skill handles branch creation as part of its Transit integration. Since the worktree already has the correct branch, the subagent's working directory ensures it operates in the right place. The fix-bug skill will detect the existing branch and skip branch creation.
After all subagents complete, summarise results in a table:
| Bug | Branch | Status | PR |
|---|---|---|---|
| T-{id}: {name} | T-{id}/bugfix-{name} | success/failed | #{pr} or — |
After reporting, offer to remove the worktrees:
git worktree remove ../{repo-name}-worktrees/T-{displayId}
Only remove worktrees for successfully resolved bugs (PR created). Keep worktrees for failed bugs so the user can investigate.
Weekly Installs
1
Repository
GitHub Stars
16
First Seen
9 days ago
Security Audits
Gen Agent Trust HubPassSocketFailSnykPass
Installed on
amp1
cline1
opencode1
cursor1
continue1
kimi-cli1
Azure Data Explorer (Kusto) 查询技能:KQL数据分析、日志遥测与时间序列处理
114,200 周安装