pr

Create, promote, and merge GitHub pull requests with verified-head commit gating.

1|1|Updated Jul 23, 2026
One-click install
npx skills add https://github.com/nearmap/shipyard --skill pr-nearmap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/nearmap/shipyard/tree/main/skills/pr
Command: npx skills add https://github.com/nearmap/shipyard --skill pr-nearmap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing a pull request's lifecycle — creating it, writing a concise description, requesting automated reviewers, reconciling review threads, and merging only the exact reviewed commit — involves many error-prone GitHub CLI and API details that are easy to get wrong. ## Core Features & Use Cases - PR Lifecycle Management: Detects branch and PR state, then creates, promotes from draft, or cleans up the PR for the current branch without ever operating on main. - Description Contract: Writes a brutally short PR body linking the tracker ticket, the why, and 2-4 summary bullets, while durable acceptance evidence lives in a separate comment that refreshes cannot erase. - Automated Reviewer Handling: Requests bot reviewers (e.g. Copilot) via a gh/GraphQL ladder, confirms the request landed, and reconciles review threads by bot author type rather than unstable login strings. - Verified-Head Merge: Merges with squash, merge, or rebase using --match-head-commit so only the CI-green, reviewed commit can land. - Use Case: After /sy:ship finishes a task, invoke this skill to promote the draft PR, request the automated reviewer, reply to its threads, and hand off a merge-ready pull request. ## Quick Start Ask the assistant to create or update the GitHub PR for the current branch, reconcile any automated reviewer threads, and report the PR URL and resulting state.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I create and promote a GitHub pull request from the command line?▼

Use the gh CLI to push the branch, create the PR, and run gh pr ready to promote it from draft. This skill detects the current state first and never operates on main, choosing create, promote, or cleanup automatically.

How to request a Copilot automated review on a GitHub PR?▼

Request it with gh pr edit --add-reviewer "@copilot" on gh 2.87.0 or newer, since raw REST review requests fail with a 422 for bot reviewers. If that fails, request by the bot's node id over the GraphQL requestReviews mutation.

Why does gh pr view show no review requests for a bot reviewer?▼

The REST-backed gh pr view --json reviewRequests renders an empty list for bot reviewers even when one is requested, producing a false negative. Confirm via the GraphQL reviewRequests query, which correctly reports Bot-type requested reviewers.

How do I merge only the exact commit that passed CI and review?▼

Pass --match-head-commit with the validated SHA to gh pr merge for squash, merge, or rebase strategies. The merge aborts if the branch head moved since validation, so a race-pushed commit can never land.

Why does posting a PR comment with -F body=@file sometimes fail?▼

gh api -f/--field posts the literal string @file instead of reading the file, silently corrupting the comment. Use -F/--raw-field key=@file or --body-file, then read the stored body back to confirm the intended prose was posted.