- name
- bug-bash
- description
- Fix a list of bugs from the tracker in this repo, one branch each, test-first, with each fix placed by its parent (on the epic's GitHub stack for a bug in an unreleased epic, or its own PR from main for a standalone bug), moving each ticket through In Progress and Ready for Release. When a fix needs another repo, hand it off with pasteable comments instead of touching it. Use when the user gives a list of bugs to fix, says "bug bash", or pastes a "Big Bug Fix Bash" prompt.
Bug Bash
Fix several bugs in one session, each on its own branch, and keep the tracker in step. Each fix goes where its bug belongs: on its epic's stack, or on its own PR from main (see "Where the branch goes").
First, load the team config with roost-config.
Inputs
Ask for anything missing, in one message:
- The bugs: ticket keys.
- This repo: which of the config's
reposthis session is in (its working directory usually says). Every other repo is off-limits. - Where each fix goes comes from the bug itself (see "Where the branch goes" below). Ask only if the user named a stack that contradicts it.
- Anything the user wants different from the defaults below.
Where the branch goes
Read the bug's parent in the tracker:
Released means the epic's code is in production, not that the epic ticket is closed: an epic can stay open after release for its person-owned tasks. It's released when its Close-out comment says what's in production (close-out-epic step 6), or its stories carry a fix version that's released. If neither says so, treat it as unreleased.
Name the branch for the ticket (PROJ-XXXX). Several bugs of the same epic stack on each other in the order given.