What problem does it solve? Managing GitHub pull requests by hand—drafting bodies, verifying local CI parity, resolving ambiguous PR versus stack numbers, publishing branches, and merging linear stacks—involves repetitive, error-prone steps that this Skill routes through one explicit subcommand interface. ## Core Features & Use Cases - PR lifecycle routing: Resolves bare numbers across PR and stack namespaces, checks out PRs or stacks into jj workspaces, and authors deterministic Conventional Commit PR titles and bodies. - Fail-closed verification: Runs exact local test/lint parity gates against immutable revision anchors before any publication, with receipts bound to head and base OIDs. - Stacked PR management: Creates, updates, reviews, and merges conventional linear PR stacks bottom-up, including namespace resolution and GitHub stack discovery. - Use Case: A developer with a jj-managed stack of three changes runs the create subcommand to publish draft PRs bottom-up, verify local CI parity per surface, and drive hosted CI to green. ## Quick Start Ask the assistant to create a draft pull request for the current saved change using the pr skill's create subcommand.