pr

Automates GitHub pull-request authoring, verification, review, stacking, and merging workflows.

4|1|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/alvis/.agents --skill pr-alvis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/alvis/.agents/tree/main/plugins/coding/skills/pr
Command: npx skills add https://github.com/alvis/.agents --skill pr-alvis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

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.

Frequently Asked Questions about pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a draft pull request from a jj change?

Use the create subcommand with an optional commit ref to publish a saved change or linear stack as draft PRs. The workflow verifies local CI parity first, pushes bookmarks bottom-up, and authors Conventional Commit titles and bodies.

How do I resolve a bare number that could be a PR or a stack?

Use the resolve subcommand, which binds the number's namespace by ordering PR and stack lookups based on the request's wording. It reports the resolved surface, the rejected candidate, and any ambiguity without mutating anything.

Does this skill support stacked pull requests on GitHub?

Yes, it loads dedicated GitHub stack references for create, update, review, checkout, and merge operations on linear stacks. Stacks publish bottom-up with per-surface verification, and merge validates the stack before merging bottom-up.

Can I skip the local CI verification gate before publishing?

Only by explicitly passing --no-verify, which skips the local revision-bound test and lint gate for that invocation and is recorded per bookmark and PR. Hosted CI, review, and all other publication gates remain mandatory.

What happens when a request omits a subcommand?

The skill prints the complete usage block and stops without inferring any remote mutation. Exactly one subcommand executes per invocation, and unknown options are rejected before any remote change.