What problem does it solve? Shipping an approved feature branch to main involves repetitive, error-prone steps: verifying the review verdict is still current, composing a rich PR body with artifact links, choosing squash-safe merge commands, and avoiding leaked commit messages. This Skill automates that final publishing step while keeping a human confirmation gate before any irreversible push or PR creation. ## Core Features & Use Cases - Review-gated publishing: Reads the verdict and last-reviewed commit from the spec's TECH.md and stops if code changed after approval, preventing unreviewed code from reaching main. - Rich PR generation: Builds a sectioned PR body (Summary, Goal, Design, Research, Phases, Verification) with SHA-pinned permalinks to spec artifacts instead of pasted copies. - Two landing modes: Default pushes the branch and opens a squash PR to main via gh; the local mode squash-merges into main and deletes the branch without touching the remote. - Use Case: After a code review approves your cluster-mcp feature branch, invoke the Skill to verify nothing changed since approval, confirm the PR title and body, and land the change on main as a single clean squash commit. ## Quick Start Ask the assistant to publish the current approved feature branch to main as a squash PR, confirming the title and body before pushing.
