pre-mergelisted

# 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 three modes. All three reuse the architectural review dimensions defined in `review-checklist.md`; they differ in what they consume and what they produce. - **Author-mode (default)** — invoked on your own branch with no `--pr` argument. The skill creates the PR (Phase 2) and prints findings to the terminal as advisories (Phase 4), then hands back there — **it makes no fix commits of its own and opens no second pass.** This is the mode auto-invoked by `/execute` Step 6 on the HITL path. **What it reads is decided by branch state, not by a flag:** a first review reads the whole branch; a re-run against a PR that already carries a review-currency stamp, whose head has since moved, takes t