pr-creation

Create GitHub pull requests with structured documentation, labels, linked issues, and verification summaries.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill pr-creation-sarkarshivaditya-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-creation
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/troykelly-claude-skills/skills/pr-creation
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill pr-creation-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull requests often lack context, missing issue links, verification evidence, or reviewer guidance, which slows reviews and creates confusion. This Skill standardizes PR creation so every pull request tells the complete story of the change. ## Core Features & Use Cases - Structured PR Templates: Generates titles, summaries, change lists, verification tables, and reviewer checklists following a consistent format. - Issue Linking and Labels: Automatically links issues with closing keywords, applies labels, and assigns reviewers via the GitHub CLI. - Special Case Handling: Supports draft PRs, breaking change callouts with migration guides, and review guides for large PRs. - Use Case: After finishing a feature branch with passing tests and clean commits, use this Skill to create a fully documented PR that closes the related issue and includes acceptance criteria verification results. ## Quick Start Create a pull request for my current branch with a full summary, linked issue, verification results, and appropriate labels.

Frequently Asked Questions about pr-creation

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

FAQPage Schema
How do I create a pull request with the GitHub CLI?

Use gh pr create with --title, --body, --base, and --head flags to open a pull request from the terminal. You can pass a heredoc for the body to include full markdown documentation with summaries, changes, and verification results.

How do I link issues to a pull request so they close automatically?

Include closing keywords like Closes #123, Fixes #123, or Resolves #123 in the PR body. GitHub automatically closes the linked issue when the PR merges, while Relates to links without closing.

What should a good pull request description include?

A good PR description includes a summary of what and why, a list of key changes, linked issues, verification results with test status, and a checklist. Large PRs benefit from a suggested review order and files grouped by category.

How do I create a draft pull request on GitHub?

Run gh pr create with the --draft flag to open a work-in-progress PR for early feedback. When the work is complete, mark it ready for review with gh pr ready followed by the PR number.

When should I rebase my branch before creating a pull request?

Rebase when your branch has fallen behind the target branch to avoid merge conflicts and keep history clean. Fetch origin, rebase onto the target, resolve conflicts, then push with --force-with-lease for a safe force push.