Menu

Individual skill

pr-description-writer

Write pull request titles and descriptions from a branch diff - problem and evidence, approach, risk and blast radius, real test evidence, rollout and rollback, a reviewer guide, before/after screenshots for UI, and correct closing keywords - inside the repo's PR template when one exists. Use when someone asks "write the PR description", "open a PR for this branch", "summarize this branch for reviewers", or "my PRs keep getting rubber-stamped". Do NOT use for reviewing someone else's PR - use code-review-checklist instead - or for individual commit messages - use git-commit-writer instead.

skills/pr-description-writer/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# PR Description Writer

A pull request description tells a time-limited reviewer what to check, what could break, and what is already verified. The costly mistake this skill prevents is the description that restates the title ("Updates the checkout flow") or lists files, forcing the reviewer to reverse-engineer intent from the diff. They either rubber-stamp it or spend an hour rediscovering context the author had - and either way the riskiest part gets the least scrutiny.

## Operating procedure

### Step 1: Gather the inputs

Collect before writing:

- The full branch diff against its base: `git diff <base>...HEAD` (three dots, so you see only this branch's changes) and `git log <base>..HEAD --oneline`.
- The motivation: linked issue, ticket, incident, or the user's own explanation. If none exists, ask. Never invent a motivation.
- The repo's PR template, if any (`.github/pull_request_template.md`, `.github/PULL_REQUEST_TEMPLATE/`, or `docs/`). If one exists, fill its headings in its order; the sections below go inside it, not around it.
- How the repo merges. With squash merges the PR title usually becomes the commit subject (GitHub's default for multi-commit PRs); check the repo's squash-message setting and follow its commit convention.