create-pr

Generate structured pull request descriptions from commit history and diff stats.

7|2|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/mthines/agent-skills --skill create-pr-mthines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/mthines/agent-skills/tree/main/skills/create-pr
Command: npx skills add https://github.com/mthines/agent-skills --skill create-pr-mthines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the generation of clear, concise, and standardized pull request descriptions, saving time and improving review clarity.

Core Features & Use Cases

  • Automated PR Summary: Creates a user-friendly markdown description with sections such as why, what changed, and how to verify.
  • Standardized Format: Ensures consistent presentation aligned with best practices for PR documentation.
  • Use Case: When a developer completes a code change, they can invoke this Skill to produce an immediate, well-structured PR description suitable for review and automation.

Quick Start

Invoke the create-pr skill to generate a concise PR description based on recent commits and diff summary, then review and submit.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I generate a pull request description from commit history automatically?

To generate a pull request description automatically, this Skill utilizes your commit history, diff stats, and metadata to produce a structured markdown summary with motivations, key changes, and verification steps.

What should a standardized PR summary include for better code review?

A standardized PR summary should include sections for why the change was made, what changed, and how to verify it, ensuring consistent presentation that improves code review clarity and collaboration.

Can I automate PR documentation for my software development workflow?

Yes, you can automate PR documentation by invoking this Skill after completing code changes to immediately produce a well-structured pull request description suitable for review and automation.

What is the best way to structure code review descriptions for my team?

The best way to structure code review descriptions is using a standardized markdown format with dedicated sections for motivations, key changes, and verification steps to streamline collaboration.

Does this automated PR generation work without external dependencies?

Yes, this automated PR generation works without external dependencies, utilizing your existing commit history and diff metadata to create professional and structured pull request descriptions.