Guards

Cleans up after merged work, once it shipped: removing a branch needs git, the forge or the user to say it merged; removing it or filling in its issue waits for the pipeline holding it to pass; merged, clean work gets a follow-up to remove its worktree and branches.

Gates git work: no commit, push or merge without the user's say-so in the current turn; a push to a branch that already landed is refused; a pushed series must leave the project working at every commit; commit messages (format and the issue it is about, then a Haiku review of the body) and MR descriptions kept tidy.

Comments worth keeping: limit-edits flags comment-heavy edits, limit-turns sends a follow-up when a turn's diff adds too many comments.

Docs worth keeping: docs-review asks Haiku whether new text will be read again, docs-no-repeat-code blocks lines that restate code, limit-docs sends a follow-up when a turn adds too much prose.

Scripts worth keeping: scripts-review asks Haiku whether a new script could just be typed again when needed.