Review Branch Until Clean
COORDINATOR SKILL. INVOKES: review-branch-logic, review-branch-style, review-branch-ui when relevant, address-codex-concerns, write-commit-name, optional enable-remote-publication.
Run a current-branch review/fix loop. Default source_branch to the current branch and base_branch to main.
Read Review Loop before editing, committing, or pushing.
USE FOR:
- "review this branch and fix the issues"
- "keep reviewing this branch until Codex has no concerns"
- "fully review, repair valid findings, and push each fix"
DO NOT USE FOR:
- Review-only approval or merge-readiness; use
review-branch-for-merge.
- Single concern sets; use
address-codex-concerns.
- CI repair, monitoring, PR publication, or merge-conflict resolution.
- Branches too large or mixed to stabilize; use
split-branch-into-stack.
Workflow
- Inspect
git status -sb, resolve base_branch, and read the branch diff.
- Run a fresh full-branch review using repo standards plus focused review skills where applicable.
- Stop if no findings remain.
- Send findings to
address-codex-concerns; fix only validated issues in one coherent batch.
- Run targeted verification.
- Stage only the batch, use
write-commit-name, commit without #CI unless the prompt explicitly asks to include a CI marker on that content commit, and push only to a verified safe target. Use a separate empty #CI trigger commit for ordinary requests to trigger CI or run GitHub Actions after the content commit is published.
- Repeat until clean or blocked by an intentional/disputed finding.
Troubleshooting
- Dirty unrelated worktree: ask which files belong.
- Unverified PR head, upstream, remote alias, or auth: use
enable-remote-publication.
- Repeated disputed finding or failed verification: stop and report.
Output
Return Markdown with review base, iteration count, repair commits, checks run, and final status. Use inline code paths, not local filesystem links.
1---2name: review-branch-until-clean3description: Review and repair the current branch against main until no Codex findings remain. Trigger for end-to-end branch review-and-fix loops. Exclude review-only, CI-only, publication-only, branch-splitting, and single-concern triage requests.4---56# Review Branch Until Clean78**COORDINATOR SKILL. INVOKES:** `review-branch-logic`, `review-branch-style`, `review-branch-ui` when relevant, `address-codex-concerns`, `write-commit-name`, optional `enable-remote-publication`.910Run a current-branch review/fix loop. Default `source_branch` to the current branch and `base_branch` to `main`.1112Read [Review Loop](references/review-loop.md) before editing, committing, or pushing.1314## USE FOR:1516- "review this branch and fix the issues"17- "keep reviewing this branch until Codex has no concerns"18- "fully review, repair valid findings, and push each fix"1920## DO NOT USE FOR:2122- Review-only approval or merge-readiness; use `review-branch-for-merge`.23- Single concern sets; use `address-codex-concerns`.24- CI repair, monitoring, PR publication, or merge-conflict resolution.25- Branches too large or mixed to stabilize; use `split-branch-into-stack`.2627## Workflow28291. Inspect `git status -sb`, resolve `base_branch`, and read the branch diff.302. Run a fresh full-branch review using repo standards plus focused review skills where applicable.313. Stop if no findings remain.324. Send findings to `address-codex-concerns`; fix only validated issues in one coherent batch.335. Run targeted verification.346. Stage only the batch, use `write-commit-name`, commit without `#CI` unless the prompt explicitly asks to include a CI marker on that content commit, and push only to a verified safe target. Use a separate empty `#CI` trigger commit for ordinary requests to trigger CI or run GitHub Actions after the content commit is published.357. Repeat until clean or blocked by an intentional/disputed finding.3637## Troubleshooting3839- Dirty unrelated worktree: ask which files belong.40- Unverified PR head, upstream, remote alias, or auth: use `enable-remote-publication`.41- Repeated disputed finding or failed verification: stop and report.4243## Output4445Return Markdown with review base, iteration count, repair commits, checks run, and final status. Use inline code paths, not local filesystem links.
willakins