bug-blitz_skill

Overview

This skill automates a parallel bug-fixing campaign by creating one git worktree and one subagent per open bug. It queries Transit for bug tasks in the "idea" status, sets up isolated worktrees per bug, and runs the fix-bug workflow concurrently to produce PRs. After all subagents finish, it summarizes results and offers cleanup of successful worktrees.

How this skill works

The skill queries Transit for tasks of type "bug" with status "idea" and asks the user to confirm which bugs to process. For each confirmed bug it creates (or reuses) a sibling worktree and branch patterned as T-{displayId}/bugfix-{kebab-name}. It then spawns one general-purpose subagent per worktree in parallel, each instructed to run the /fix-bug skill inside its worktree. When subagents finish, the skill aggregates statuses and presents a concise table of branch, status, and PR links, then offers to remove worktrees for successful fixes.

When to use it

• You want to fix many open bugs at once without disrupting the main repo.
• You need isolated environments per bug so fixes don’t conflict.
• You want to run identical automated fix workflows in parallel.
• You have multiple small bug tickets in Transit labeled idea.
• You prefer worktrees over branching inside the main working directory.

Best practices

• Confirm and optionally exclude specific tickets before starting to avoid unwanted changes.
• Keep worktrees in a sibling ../{repo-name}-worktrees/ directory to protect the main repo.
• Let subagents run in parallel but monitor resource usage if your machine is limited.
• Only remove worktrees after a successful PR is created; retain failed worktrees for debugging.
• Use clear, descriptive task names so generated kebab-case branch names remain meaningful.

Example use cases

• Run a single command to attempt fixes for all Transit bugs in idea status before a release sweep.
• Triaging a backlog: quickly surface which bugs can be auto-fixed and which need manual work.
• CI-assisted bug blitz where each subagent runs linters, tests, and the fix-bug flow in isolation.
• Onboarding: let a junior developer review per-bug worktrees and the corresponding PRs.