skills.rest
RorySullivan1
RorySullivan1COMMUNITY
Explore all skills by this author →
GitHub

github-pull-requests

Creates and formats GitHub pull requests with titles, bodies, templates, and issue links.

Updated Jul 25, 2026
Search Tags:#git#code review#pull request#pr template#github#gh cli#issue linking
One-click install
npx skills add https://github.com/RorySullivan1/powerapp_taskmaster --skill github-pull-requests-rorysullivan1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pull-requests
Source: https://github.com/RorySullivan1/powerapp_taskmaster/tree/main/.claude/skills/github-pull-requests
Command: npx skills add https://github.com/RorySullivan1/powerapp_taskmaster --skill github-pull-requests-rorysullivan1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a finished branch into a reviewable pull request requires writing a clear title, a body that matches the actual diff, honoring repo PR templates, and linking issues correctly — work that is often rushed or skipped, leaving reviewers without context. ## Core Features & Use Cases - PR Title and Body Authoring: Writes imperative, changelog-style titles (matching Conventional Commits when the repo uses them) and structured bodies covering summary, changes, testing, and notes. - Template Detection and Filling: Detects PR templates under .github/ or docs/ and fills their sections from the actual diff rather than writing a freeform body. - Issue Linking and Review Mechanics: Adds closing keywords (Closes #N), chooses draft vs. ready, and creates or updates PRs via the GitHub MCP tools or the gh CLI. - Use Case: After pushing a feature branch, ask for a PR and receive a template-compliant description that accurately reflects the diff, links the tracked issue, and is marked draft while CI is still running. ## Quick Start Open a pull request for my current branch against main with a title and body that follow the repo's PR template and close issue #42.

Frequently Asked Questions about github-pull-requests

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

FAQPage Schema
How do I write a good pull request description?▼

Structure the body around summary, changes, testing, and notes, and make sure it describes the actual diff rather than your original plan. If the repository ships a PR template, fill its sections instead of writing freeform text.

How do I link a GitHub pull request to an issue so it auto-closes?▼

Use closing keywords like "Closes #12", "Fixes #12", or "Resolves #12" in the PR body, one per issue. These only auto-close when the PR targets the default branch; use "Refs #12" when the issue should stay open.

When should a pull request be opened as a draft?▼

Open a draft when the work is in progress, you want early feedback, or CI is not yet green. Mark it ready for review only when you would be comfortable merging it as-is.

Can I update a pull request title and body after opening it?▼

Yes, edit the existing PR using the GitHub MCP update_pull_request tool or "gh pr edit" rather than closing and reopening. This preserves the review history and comment threads.

Will this open a pull request automatically after pushing a branch?▼

No, a PR is only created when the user explicitly asks for one. Pushing a branch or finishing a feature is not treated as consent, and the skill asks when unsure.

Related Skills

Explore More Software Engineering Skills→
rpamisrpamis
2.9k

comet-safe-delivery

Commits, pushes, and delivers scoped Git changes while protecting unrelated worktree modifications.

Official
Intermediate
aadorianaadorian

update-pr

Reconcile incoming commits and publish updates to an existing pull request.

Community
Intermediate
SoSoBurnerSoSoBurner

ship

Automate code deployment by running tests, reviewing diffs, and creating a pull request.

Community
Advanced
nudgebeenudgebee
381

review-pr

Analyze pull request diffs and post review comments via GitHub CLI.

Official
Advanced