pr

Publish repository changes as ready-for-review GitHub pull requests with evidence-backed descriptions.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/hkw2028/toy-project --skill pr-hkw2028
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/hkw2028/toy-project/tree/main/.agents/skills/pr
Command: npx skills add https://github.com/hkw2028/toy-project --skill pr-hkw2028

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning local work into a reviewable GitHub pull request involves many error-prone steps: committing only the intended changes, syncing with the right base branch, avoiding duplicate PRs, and writing a body reviewers can actually understand. This Skill handles the entire publication workflow and stops before merge. ## Core Features & Use Cases - End-to-end PR publication: Commits in-scope changes as logical Conventional Commits, rebases onto the fetched target base, publishes the branch safely, and opens a ready-for-review PR against the named base or the remote default branch. - Duplicate and state awareness: Reuses an existing PR for the same head and base, and reports the current state instead of duplicating work already merged or open. - Evidence-grounded PR bodies: Writes reviewer-oriented descriptions with before-and-after behavior, alternatives and trade-offs, and verified screenshots or videos uploaded as GitHub attachments, with sensitive data redacted before upload. - Use Case: You finished a search UI change in a detached worktree with unrelated files present. The Skill creates a branch, commits only your change, rebases on the remote default branch, attaches verified before/after screenshots, and hands you the ready PR URL. ## Quick Start Ask the assistant to publish the current changes as a ready-for-review pull request against the repository's default branch without merging.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I create a GitHub pull request from uncommitted local changes?

The Skill commits the in-scope changes as logical Conventional Commits, rebases onto the fetched target base, publishes the branch, and opens a ready-for-review PR. Unrelated files and sensitive files like .env are kept out of the history.

What happens if a pull request already exists for my branch?

The Skill detects an existing open PR for the same head and base and reuses it instead of creating a duplicate. It updates the body and evidence to match the final change and reports the existing URL.

Can I create a pull request from a detached HEAD state?

Yes. Work on a detached or protected checkout is moved to a suitably named branch before publication, so no commits are lost. The branch is then based on the fetched target and pushed without overwriting unexpected remote work.

Does the Skill merge the pull request after creating it?

No. The Skill stops at a ready-for-review pull request and reports its URL, base, and head branch. Merging, required reviews, and release decisions are explicitly outside its authority.

How are screenshots handled in pull request descriptions?

Actual base and head captures at matching viewport and state are uploaded as GitHub attachments and embedded side by side. Media is inspected for credentials or personal data before upload, and unavailable baselines are stated honestly rather than fabricated.

What if the base branch is not named in the request?

The Skill resolves the remote's advertised default branch, such as master instead of main, and targets the pull request against it. It never assumes a hardcoded branch name.