When the dispatcher has audit findings filed as GitHub issues and needs to decide how to fire per-finding runners -- use this to read the labeled finding-issues, apply the status/in-progress label before dispatch, and choose parallel vs sequential runner…
Before starting any dispatched or non-trivial work that will become a PR -- open the draft PR first, with the plan as the body. The PR body is the plan, the commit stream is the work, and the PR exists as a visible, resumable work unit from minute zero. Use…
Before making any non-trivial code, docs, or config change -- create a feature branch first, then open a PR. Never commit directly to main. Apply by default before any edit; this is the baseline branch discipline that all other git skills build on.
When writing any issue, PR, or commit message, use this for the authoring standard. Covers structure (headings, lists, tables, fenced blocks, the bug block, the before/after) and voice (factual, no emdashes, no editorializing labels, conventional-commit…
The cross-project standard for issue and PR handling: conventional-commit prefixes on branches, issue titles, PR titles, and commit subjects; a label taxonomy capped at four axes (priority, area, status, size); and the claim protocol that pairs a…
When the issue or PR queue has open unlabeled items -- run a read-only triage pass that labels each one by component, category, priority, and size, flags duplicates, closes noise, and reports the p1 queue before runners are dispatched.
The two report shapes for a unit of work: the plan report written before the work starts (the draft PR body) and the completion report written when it ends (the return summary and the ready PR). Both are mechanical -- a verdict line, a labeled block of…
Use when deciding whether to dispatch a runner or a worker for a subtask. Describes the decision boundary, the failure mode when runner is used where worker is intended, and the safe composition pattern.