What problem does it solve? It enforces a controlled, manual gate between finishing implementation and opening a pull request, preventing premature or unverified PRs by checking branch state, upstream synchronization, and QA evidence before anything is created. ## Core Features & Use Cases - Branch and target validation: Resolves the PR target from the ticket's Integration Branch section, parent epic, or base_branch, and verifies the current branch matches the expected pattern, is clean, and is fully pushed. - QA evidence gating: For backend-orchestration opt-ins, validates accepted QA evidence for the exact current commit SHA via the coordinator CLI before allowing any PR action. - PR body preparation and tracker integration: Builds the PR body from the git-workflow template, stores it in .claude/tmp/, opens the PR/MR through the tracker CLI with the correct Closes/Related-to keyword, and publishes completion reports when required. - Use Case: After /implement finishes a ticket branch, the developer runs this command to confirm the branch is synced, QA evidence is accepted, and then open a properly linked pull request without ever auto-merging. ## Quick Start Ask the agent to open a pull request for the current ticket branch after /implement has finished and the branch has been pushed.
