prs · git:20261108.04648e3 · 2026-11-08 · sha256 363a336856070bb1
prs git:20261108.04648e3A
Immutable. This exact content never changes and is served at /api/v1/blob/363a336856070bb1.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ylqer6wggumun5ph/363a336856070bb1bee07644a6636a4e6385496264a4f40631d3e5aa578daea5.json
Then /plugin install prs@markdownregistry-ylqer6wggumun5ph in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: prs description: Use when opening or landing a pull request, or changing its title or description. --- # Pull requests A pull request delivers one coherent outcome, together with the migrations, tests, and supporting changes it needs. It lands as one commit, so propose separate pull requests for independent outcomes. ## Draft and ready CI runs the full gate only on pull requests marked ready. Keep a pull request in draft while work continues, and mark it ready with `gh pr ready` once the repository gate passes locally on the final commit. Each move to ready starts a full run, so convert it back with `gh pr ready --undo` before pushing more changes. Unless you are about to land the pull request, report that run as pending instead of waiting for it. ## Title and description Pull requests squash into main with the title as the commit subject and the description as the commit body, so keep both accurate until the merge. The title is a Conventional Commit subject, `type(scope): description`, with an optional scope and an imperative description. Write the description for whoever decides on the merge. Open with these two short paragraphs and nothing above them, because they should be enough to decide on: ```md **Before.** The current state, who or what it affects, and its concrete cost or risk. **Now.** The resulting state and how it resolves that problem. ``` For a new capability, `Before` names the missing ability, the current workaround, or the cost or risk of going without it. That the feature didn't exist gives the decider nothing to weigh. When behavior stays the same, as in a refactor, `Before` gives the reason for the change and `Now` says that behavior is unchanged. When the pull request resolves an issue, the issue already holds the problem and its evidence. Summarize the problem in a sentence and link the issue with `Closes #<number>` instead of restating it. Add further sections only when the change needs them: - `## Implementation` gives the details needed to review the implementation. - `## Breaking change` names the affected consumers and the migration each must make. - `## Screenshots` belongs to the `screenshots-in-prs` skill, which applies to any change to rendered UI. End the description with one line naming what opened the pull request: the model with its version, the agent harness, and any app that wraps the harness, such as `Opened by Claude Opus 5.5 in Claude Code via T3 Code.` Take each from your context, and write `unknown` for anything it doesn't state rather than guessing. Keep the line when another agent updates the description. ## Verification Always include `## Verification` with `### Completed checks`: one line per check, naming what ran and how much of it passed, including partial runs and failures. Add `### Check it yourself` only when a reviewer can confirm the behavior interactively or visually. Give the exact `gh pr checkout <number-or-branch>` command, the shortest steps, and the expected result. ## Landing Before landing a pull request of any size, run the `review-fix` skill if you judge that a reviewer could find a bug in it that someone would otherwise run into. Standards syncs are exempt, because a consumer can't change synced files. Land with `bun standards land <pr>`, or `bunx @davidvornholt/standards land <pr>` in a repository without a Bun workspace, never with `gh pr merge`. GitHub can't require checks in private repositories on its free plan, so `land`'s wait for them may be the only gate.