/pr-prep — Prepare PR for Merge

Full pre-merge workflow: rebase, quality suite, acceptance criteria audit, code review, PR creation, and post-merge cleanup. Run this after /human-test passes.

Usage: /pr-prep 42

This command orchestrates: /verify → /code-review → /create-pr → cleanup.

Step 1 — Sync with main

bash
1git fetch origin main
2git rebase origin/main

If there are conflicts, resolve them carefully. For any non-obvious conflict, ask the user for guidance rather than guessing at intent.

Step 2 — Full quality suite

bash
1/verify

All checks must be green before proceeding. Fix anything failing.

Step 3 — Quality gate confirmation

Before running the code review, confirm the required gates have been run. Check the PR description for these checkboxes — if either is unchecked and not marked N/A, stop and run them now.

bash
1gh pr view $ARGUMENTS --json body --jq '.body'

Gates required before merge:

• /security-review — mandatory if the diff touches: auth, sessions, JWT, user data, payments, file uploads, external integrations, or any new API route
• /performance-review — mandatory if the diff touches: database queries, findMany, list/table rendering, search endpoints, background jobs, or package.json

If either applies and hasn't been run: run it now and address findings before proceeding.

Step 4 — Acceptance criteria audit

bash
1gh issue view $ARGUMENTS

Go through every acceptance criterion and confirm it is satisfied:

Final Acceptance Criteria Audit — Issue #[N]:
✅ [Criterion 1] — [test name or observable behavior]
✅ [Criterion 2] — [test name or observable behavior]
✅ TypeScript: no errors
✅ All tests passing

If any criterion is unmet, fix it now. Do not proceed with an unmet criterion.

Step 5 — Code review

bash
1/code-review

Address any Critical or Warning findings before marking the PR ready.

Step 6 — Create / finalize PR

bash
1/create-pr

Step 7 — Wait for approval and merge

CI will run. Once a reviewer approves and all checks are green, the PR can be merged.

Merge strategy: squash merge — keeps main history clean, one commit per feature.

Step 8 — Post-merge cleanup

Once merged:

bash
1# Remove the worktree (run from the main repo directory, not the worktree)
2git worktree remove [worktree-path]
3git branch -d [branch-name]

Close the issue if not auto-closed by "Closes #N":

bash
1gh issue close $ARGUMENTS \
2  --comment "Completed in PR #[pr-number] — merged to main."

Check if the milestone is now complete:

bash
1gh issue list --milestone "[milestone-name]" --state open

If all issues are closed:

bash
1gh api repos/:owner/:repo/milestones/[milestone-number] \
2  --method PATCH \
3  --field state="closed"

Step 9 — What's next

bash
1/parallel-status

See what other features are in progress, what's ready to start, and what needs attention.