PR Prep
Bring one branch or PR to readiness. By default, publish it as ready for review
and leave merging to the caller. Honor an explicit request to keep it in draft.
Stack management stays with the caller.
/pr-prep yolo authorizes merging this PR once it meets the repo’s merge
requirements, including after fixes made during this run. No further merge
confirmation is needed. An explicit request to keep the PR in draft takes
precedence over yolo.
Scope. Resolve the branch, immediate base, intended changes, existing PR,
and whether draft or yolo was requested. Preserve unrelated work.
Review. Run /review-fix-loop <immediate-base> over the complete PR diff.
Continue when review and verification pass; report blockers.
Publish. Read publish.md. Commit the task’s
changes, push, and create or update the PR. Record the remote head and base.
Watch. Read ci.md for checks and
pr-feedback.md when feedback exists. Watch the
current pushed head and triage findings through /review-sweep. Hold replies
claiming a fix and thread resolution until that fix is pushed.
Repeat or finish. If you make fixes, return to step 3. After publishing,
post held replies and resolve eligible threads, then check CI and feedback
again. Finish when the current published changes pass the needed checks and
have no outstanding accepted fixes. Account for missing checks and open
threads; report pending human approval or other blockers. For a draft, use
the draft completion rules in the references.
Merge with yolo. Once ready, read merge.md and
merge the PR. After GitHub confirms the merge, run /post-merge-cleanup
with the PR, merge commit, branch, base, worktree, and known task-owned
resources. Without yolo, stop at readiness.
Report the PR link, current head, verification results, readiness or merge
result, cleanup result, and anything still needed.
1---2name: pr-prep3description: Prepare one branch or PR for review, handle CI and feedback, and optionally merge when invoked with yolo.4---56# PR Prep78Bring one branch or PR to readiness. By default, publish it as ready for review9and leave merging to the caller. Honor an explicit request to keep it in draft.10Stack management stays with the caller.1112`/pr-prep yolo` authorizes merging this PR once it meets the repo’s merge13requirements, including after fixes made during this run. No further merge14confirmation is needed. An explicit request to keep the PR in draft takes15precedence over `yolo`.16171. **Scope.** Resolve the branch, immediate base, intended changes, existing PR,18 and whether draft or `yolo` was requested. Preserve unrelated work.19202. **Review.** Run `/review-fix-loop <immediate-base>` over the complete PR diff.21 Continue when review and verification pass; report blockers.22233. **Publish.** Read [publish.md](references/publish.md). Commit the task’s24 changes, push, and create or update the PR. Record the remote head and base.25264. **Watch.** Read [ci.md](references/ci.md) for checks and27 [pr-feedback.md](references/pr-feedback.md) when feedback exists. Watch the28 current pushed head and triage findings through `/review-sweep`. Hold replies29 claiming a fix and thread resolution until that fix is pushed.30315. **Repeat or finish.** If you make fixes, return to step 3. After publishing,32 post held replies and resolve eligible threads, then check CI and feedback33 again. Finish when the current published changes pass the needed checks and34 have no outstanding accepted fixes. Account for missing checks and open35 threads; report pending human approval or other blockers. For a draft, use36 the draft completion rules in the references.37386. **Merge with `yolo`.** Once ready, read [merge.md](references/merge.md) and39 merge the PR. After GitHub confirms the merge, run `/post-merge-cleanup`40 with the PR, merge commit, branch, base, worktree, and known task-owned41 resources. Without `yolo`, stop at readiness.4243Report the PR link, current head, verification results, readiness or merge44result, cleanup result, and anything still needed.
sreejithraman