pull-request

Generate pull request descriptions following repository templates.

Updated Sep 20, 2025
One-click install
npx skills add https://github.com/yellow-seed/crypto_wallet_tool --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/crypto_wallet_tool/tree/main/.github/skills/pull-request
Command: npx skills add https://github.com/yellow-seed/crypto_wallet_tool --skill pull-request-yellow-seed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams produce polished pull requests by ensuring PRs follow a consistent template, reducing back-and-forth and speeding up approvals.

Core Features & Use Cases

  • PR template enforcement: Generate PR descriptions that align with .github/PULL_REQUEST_TEMPLATE.md.
  • What/Why/How reasoning: Provide clear summaries, rationale, and implementation details referencing commits and related issues.
  • Use Case: When preparing PRs that touch multiple files or relate to a specific Issue, generate concise summaries, change lists, and testing notes to streamline reviews.

Quick Start

Use this skill to create a high-quality PR description from the current branch and recent commits.

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 pull request description that follows my repository's template?

Pull request templates standardize PR descriptions across your repository. This skill generates descriptions aligned with your .github/PULL_REQUEST_TEMPLATE.md, ensuring consistent structure with what/why/how sections that reviewers expect, reducing revision cycles.

What should I include in a pull request to speed up code reviews?

Effective PRs include a clear summary of changes, rationale for the implementation, references to related issues, and testing notes. This skill produces concise PR descriptions with these elements automatically, helping reviewers understand context quickly and approve faster.

Can I generate a PR description from my recent commits and branch changes?

Yes. This skill analyzes your current branch and recent commits to generate a polished PR description that details what changed, why it changed, and how it was implemented, eliminating manual summarization.

How do I link issues and commits in my pull request description?

Pull request descriptions should reference related issues and commits for traceability. This skill automatically incorporates commit details and issue references into structured PR descriptions that align with GitHub workflows.

When should I use a standardized PR template instead of writing freeform descriptions?

Standardized templates reduce review delays, ensure consistency across teams, and prevent important information from being omitted. Use templated PRs when working on projects with multiple contributors or strict review requirements.