write-pr

Drafts pull request bodies in a structured style from branch diffs and commits.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/GregM1991/skills --skill write-pr-gregm1991
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-pr
Source: https://github.com/GregM1991/skills/tree/main/skills/write-pr
Command: npx skills add https://github.com/GregM1991/skills --skill write-pr-gregm1991

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing clear, consistent pull request descriptions is time-consuming, and reviewers often receive vague or incomplete PR bodies. This Skill drafts a PR body in a fixed, reviewer-friendly structure so every PR communicates what changed, why it matters, and how to verify it. ## Core Features & Use Cases - Structured PR Body Generation: Produces required ## Summary and ## Why this matters sections, plus an optional ## QA section with manual verification steps. - Context-Aware Drafting: Uses user-provided context, or inspects the current branch diff, recent commits, issue links, and relevant files when context is missing, without inventing details. - Style Enforcement: Writes in ASD-STE100 Simplified Technical English and delegates tone to the writing-style and unslop skills. - Use Case: After finishing a feature branch, ask for a PR body and receive a concise summary of the code changes, the rationale, and step-by-step QA instructions for reviewers. ## Quick Start Draft a PR body for my current branch using the changes in this diff.

Frequently Asked Questions about write-pr

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

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

A good pull request description includes a Summary section listing the main code changes, a Why this matters section explaining the problem solved, and optionally a QA section with manual verification steps. This Skill generates that structure from your branch diff or provided context.

How to generate a PR body from a git branch diff?▼

Provide no context and the Skill inspects the current branch diff, recent commits, issue links, and relevant files before drafting. It does not invent details, so the generated body reflects only the actual changes.

What sections should a pull request body include?▼

This Skill requires a Summary section with a high-level overview and bullet list of changes, and a Why this matters section explaining the rationale. A QA section with manual functional verification steps is optional, while Review and Validation sections are excluded.

Can the PR body include test or build commands for reviewers?▼

No. The QA section excludes repo, build, and verification commands such as npm, npx, yarn, test runners, linters, and type-checkers. It focuses purely on manual functional verification steps like navigation flows, accounts, fixtures, and feature flags.

What happens if the writing-style or unslop skills are not available?▼

The Skill stops and reports that the required skills are missing instead of drafting. It depends on the writing-style and unslop skills being loaded before it produces any PR body.