Pull request writer

Draft a PR title, summary, and test plan from a diff so reviewers know what to check.

Install in Claude Code

Create a folder whose name matches the skill name field (pull-request-writer/). Save the text below as SKILL.md inside it. Personal skills go in ~/.claude/skills/pull-request-writer/. Project skills go in .claude/skills/pull-request-writer/. Claude Code discovers them from the filesystem.

Upload on claude.ai

Zip the skill folder (the zip should contain the folder, which contains SKILL.md) and upload it in Claude’s Skills settings. Anthropic’s current platform docs list custom uploads on Pro, Max, Ultra, Team, and Enterprise plans when code execution is enabled. Check the Claude Help Center for the latest plan details. Read the files before you turn a skill on.

Use with the Claude API

Custom API Skills are uploaded through the Skills API and referenced with the code execution tool. Skills do not sync automatically from Claude Code or claude.ai — install this folder again on the surface where you need it. See Anthropic’s Agent Skills overview.

---
name: pull-request-writer
description: Drafts pull request titles, summaries, and test plans from a diff, commit list, or issue description. Use when the user asks for a PR description, merge request writeup, or help explaining a change to reviewers.
---

# Pull request writer

## Goal
Write a PR description that helps a reviewer decide what to read and what to test. Be concrete about behavior change. Do not hide risk.

## Workflow
1. Gather the diff, commit subjects, linked issue text, and any notes the user provides.
2. State the user-facing or systems-facing change in one sentence.
3. Explain why the change exists. Quote an issue or bug report only if the user supplied it.
4. List important implementation choices and any follow-ups intentionally left out.
5. Call out risk: migrations, auth, payments, data deletion, public API changes, or feature flags.
6. Write a test plan a reviewer can actually perform.

## Output template
```markdown
## Title
type: short imperative summary

## Summary
[1 short paragraph]

## Why
[Problem or opportunity. Link or issue ID only if provided.]

## What changed
-
-

## How to test
- [ ]
- [ ]

## Risk and rollout
- Risk:
- Rollback:
- Flags or migrations:

## Screenshots or notes
[Include only if the user provided them or asked for placeholders.]
```

## Rules
- Title should stand alone in a PR list. Avoid "misc fixes" and "updates".
- Do not claim tests were run unless the user said so.
- If the diff looks unrelated (formatting plus a logic change plus a dependency bump), suggest splitting the PR.
- Keep the tone neutral and specific. Thank-you notes and emoji are optional and only if the repo's existing PRs use them.

You may copy and adapt this free skill for personal or commercial use. If you republish it, please credit Skillory with a link. Audit any skill — including this one — before enabling it in an environment with access to private data.

Related skills

Claude Engineering SKILL.md

Changelog writer

Turn commits and merged PRs into a readable changelog grouped the way users scan it.

Open skill →

Claude Engineering SKILL.md

Code review

Review a diff like a careful teammate: correctness first, then security, then clarity.

Open skill →

Claude Engineering SKILL.md

Git commit messages

Write conventional commit messages from a staged diff, without fluff or invented ticket IDs.

Open skill →