What problem does it solve? Opening a pull request involves many easy-to-miss steps — title format, draft state, base branch, reviewer assignment, and pre-publish checks — and silent failures (like GitHub dropping a reviewer request) leave work waiting for a review nobody was asked to give. ## Core Features & Use Cases - PR Title and Branch Conventions: Enforces the [<KEY>-<number>] <what was done> title format matching the task and branch name, keeping commit type/scope out of the PR title. - Draft vs. Ready Workflow: Reads the CI pipeline file to decide whether the PR opens as a draft (pipeline runs on that base) or directly, and lifts the draft with gh pr ready only when checks pass. - State Verification: Re-reads PR state via the GitHub API after reviewer/label calls and before reporting anything, since return codes can be zero even when nothing happened. - Pre-Publish Checklist: A 15-item checklist covering base freshness, diff scope, builds, translations, PR body sections, and board column moves. - Use Case: An agent finishing a task branch uses this pattern to open a draft PR against the epic branch, verify the reviewer and labels were actually set, pass the checklist, lift the draft, and move the task to in-review. ## Quick Start Open a pull request for the current branch following the git-workflow-pr pattern, including title format, draft handling, and the pre-publish checklist.
