skills.rest
stephendolan
stephendolanCOMMUNITY
Explore all skills by this author →
Website𝕏@Stephen_DolanGitHub

pull-request

Draft concise GitHub pull request descriptions with summary and problem sections.

2|Updated May 15, 2015
Search Tags:#automation#git#code review#development workflow#pull request#github#communication
One-click install
npx skills add https://github.com/stephendolan/dotfiles --skill pull-request-stephendolan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/stephendolan/dotfiles/tree/main/claude/skills/pull-request
Command: npx skills add https://github.com/stephendolan/dotfiles --skill pull-request-stephendolan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing clear, concise pull request descriptions can be time-consuming, often leading to verbose or incomplete information that slows down review cycles. This Skill automates the generation of focused PR descriptions, ensuring essential information is communicated without overwhelming reviewers, saving time and accelerating merges.

Core Features & Use Cases

  • Concise Description Generation: Creates focused PR descriptions with only essential summary and problem statements.
  • "Core Changes" Guidance: Advises when to include a "Core Changes" section (only for major architectural shifts).
  • Context Gathering: Guides you to review changes and verify problem statements for accuracy.
  • Use Case: Automatically draft a GitHub pull request description for your latest feature or bug fix, ensuring it's brief, impactful, and adheres to best practices.

Quick Start

Generate a pull request description for my current changes, focusing on the summary and problem statement.

Frequently Asked Questions about pull-request

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

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

A concise pull request description focuses on a two-section summary and problem statement, omitting technical details and implementation specifics. This approach communicates essential information to reviewers without overwhelming them, accelerating code review cycles and merges.

When should I include a Core Changes section in my PR?▼

Include a Core Changes section only for major architectural shifts or significant restructuring. For standard changes and minor fixes, stick to the summary and problem statement to keep your PR description brief and focused.

What should I exclude from a pull request description?▼

Exclude technical details, testing notes, and implementation specifics from your PR description. Focus instead on the summary of what changed and the problem it solves, keeping reviewers' attention on the essential information.

How do I use this Skill with GitHub's gh pr create command?▼

Use this Skill to automatically draft a focused PR description when creating a pull request via gh pr create. It guides you to verify your changes and problem statement, then generates a brief summary formatted for GitHub pull requests.

Can I use this for both feature additions and bug fixes?▼

Yes, this Skill applies to both features and bug fixes. It generates concise descriptions with summary and problem statements for any standard change, helping you communicate the purpose and impact clearly without unnecessary detail.

Related Skills

Explore More Software Engineering Skills→
BSteffaniakBSteffaniak

commit-message-staged-write

Generate Git commit messages from staged changes and write them for commit tools.

Community
Intermediate
robinebersrobinebers
46

shepherd

Automate GitHub pull request review management until human approval.

Community
Advanced
DevQwietDevQwiet

create-pr

Generate GitHub pull request titles and descriptions from git logs and branch changes.

Community
Basic
monaccodemonaccode
30

changelog-automation

Generate change logs from Git commit messages in Keep a Changelog format.

Official
Intermediate