skills.rest
yellow-seed
yellow-seedCOMMUNITY
Explore all skills by this author →
GitHub

pull-request

Generates template-compliant GitHub pull requests from branch commit history.

1|Updated Feb 16, 2025
Search Tags:#git#code review#pull request#pr template#conventional commits#github#gh cli
One-click install
npx skills add https://github.com/yellow-seed/my-portfolio --skill pull-request-yellow-seed
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/yellow-seed/my-portfolio/tree/main/.github/skills/pull-request
Command: npx skills add https://github.com/yellow-seed/my-portfolio --skill pull-request-yellow-seed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing clear, consistent Pull Request descriptions is time-consuming, and reviewers often receive vague PRs lacking context, test plans, or issue links. This Skill analyzes your branch's commit history and diff to produce a structured PR that follows the repository's PULL_REQUEST_TEMPLATE.md format. ## Core Features & Use Cases - Commit History Analysis: Inspects branch commits and diffs with git commands to extract What/Why/How for the PR body. - Template-Compliant Generation: Produces Summary, Type of Change, Related Issues, Changes, Test Plan, and Checklist sections matching the project template. - Issue Linking & Self-Review: References related Issues with Closes/Fixes keywords and integrates a self-review step before PR creation via the gh CLI. - Use Case: After finishing a feature branch with several commits, ask for a PR and receive a complete, reviewer-ready description with a test plan checklist and correct issue references, created directly with gh pr create. ## Quick Start Create a pull request for my current branch following the repository's PR template.

Frequently Asked Questions about pull-request

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

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

Use the GitHub CLI with `gh pr create --title "..." --body "..."` after committing your branch. This Skill builds the title in Conventional Commits format and generates the body from your commit history and diff.

How to write a good pull request description?▼

A good PR description states What changed, Why it changed, and How it was implemented. Include a Summary, Type of Change, Related Issues, detailed Changes grouped by file, and a Test Plan checklist so reviewers can verify the work.

How do I link a pull request to a GitHub issue?▼

Add keywords like `Closes #123` or `Fixes #123` in the PR body to automatically close the issue on merge. Use `Related to #123` for issues that should stay open after merging.

Does this work with repositories that have a PR template?▼

Yes, the Skill reads the repository's .github/PULL_REQUEST_TEMPLATE.md and structures the generated PR body to match its sections, including Summary, Changes, Test Plan, and Checklist.

What should I check before creating a pull request?▼

Review the branch diff with `git diff main...HEAD`, run a self-review of your changes, confirm tests pass, and verify the checklist items such as style guide compliance and documentation updates before running gh pr create.

Related Skills

Explore More Software Engineering Skills→
luyzkkluyzkk

git-workflow-and-versioning

Enforce conventional commits, atomic save-point commits, and short-lived branches.

Community
Advanced
taracodlabstaracodlabs
799

github-pr-workflow

Manages the full GitHub pull request lifecycle using the gh CLI.

Official
Intermediate
arndvsarndvs

pr-preflight

Audits changed files, diffs, and stack tooling before opening a pull request.

Community
Advanced
kotahashihamakotahashihama

split-prs

Splits large changes into stacked branches and links them as GitHub PR stacks using gh stack.

Community
Intermediate