stormlightlabs/thunderstorm
Run GitHub issues through triage, decomposition, implementation, review, and revision.
Write commit messages and pull request descriptions for this repository. Use when committing, opening a pull request, or asked to write a PR body or a pull request comment.
Cut an idea, a spec, or a finding into the issues a run takes, the sub-issues that implement them, and a milestone where the work needs more than one run. Use for /decompose or when work is understood well enough to file but has not been filed.
Read and write thunderstorm board state through tstorm board. Use when claiming an issue, changing its status, filing a sub-issue, recording a dependency, or reading what is queued.
Work a GitHub issue end to end on its own branch and open a pull request against main. Use for /implement or when asked to start work on an issue number.
Review a pull request or branch and post findings as comments. Runs a standard pass or an adversarial pass. Use for /rev, /adv-rev, code review, PR review, or when asked to check a diff for defects before merge.
Address review comments on an open pull request and push the fixes. Use for /revise or when asked to respond to review feedback on a PR number.
Think through a design, feature, or problem in conversation before any code or spec exists, and record the result as an idea file. Use for /rubber-duck, ideation, design discussion, or working out an approach.
Turn an idea into a design document a decomposition can read. Use for /specify or when an idea cannot yet produce issues because something has to be decided first.
Run one thunderstorm loop over an issue and its sub-issues. Dispatches work, tracks status, reports, and stops. Use for /thunderstorm or when asked to run an issue with sub-issues.
Read the whole board and rank what to dispatch next, as lanes that several threads can work at once. Use for /triage, for deciding what to work across parent issues, or before dispatching more than one thread.
Decide whether a unit of agent work needs its own git worktree, then create, use, and remove it with Rust build isolation. Use when starting work on an issue, running parallel agents, or cleaning up after a run.
Write, revise, and deslop documentation for this repository in plain technical English. Use for internal plans and specs, README, skills, error messages, and any prose where AI writing tells, density, or readability matter.