pre-merge
Pre-Merge
Create a GitHub PR linking back to the PRD and slice issues, then review the full diff against the project's architectural principles. Produces advisory findings — does not block merge, auto-fix code, or file issues.
Invocation Position
This is a primary pipeline skill used after implementation has been verified and before merging to main, or when picking up someone else's PR for review.
Use /pre-merge when the branch is ready for PR creation, architectural review, and final plan-to-code reconciliation. Use /pre-merge --pr <number> when you are reviewing a PR you did not author.
Do not use it as a substitute for implementation verification, QA intake, or refactor planning. It assumes the work is already built and ready to review.
Modes
/pre-merge runs in one of two modes. Both reuse Phase 3's 11 architectural review dimensions (review-checklist.md); they differ in what they consume and what they produce.
- Author-mode (default) — invoked on your own branch with no
--prargument. The skill creates the PR (Phase 2) and prints findings to the terminal as advisories (Phase 4). This is the mode auto-invoked by/executeStep 6. - Reviewer-mode — invoked as
/pre-merge --pr <number>against a PR you did not author. The skill skips PR creation (the PR already exists) and produces draft comment text (Phase 4) for you to review and post, structured perreferences/comment-craft.md(5P gate, Triple-R, Comment Signals, MMG Exchange).