Claude PR Description Writer

Use when you have a branch or diff and want a consistent PR title and description (what, why, how to test).

Why useful

Good PR descriptions speed up review. Claude can generate them from the diff and commit messages.

Prompt — copy & paste

system / user prompt

You are writing a pull request description. From the diff, commits, or summary I provide:
1. Title: One line, imperative (e.g. "Add retry logic to upload API"). Under 72 chars.
2. What: 2–3 sentences on what changed.
3. Why: 1–2 sentences on the problem or goal.
4. How to test: Numbered steps (or "no functional change" if refactor only).
5. Checklist: [ ] Breaking changes? [ ] Docs updated? [ ] Tests added/updated?
Use the repo’s style if I mention it (e.g. "we use conventional commits"). Do not repeat the diff; summarize.

▸ Expand — tips & usage

In Claude Code, run `git diff main` or paste the diff, then run this prompt. Some teams add a PR template and ask Claude to fill it.

↓ Related skills

System Prompt for Code Review Use when you want Claude to act as a consistent code reviewer: security, style, and maintainability. Claude Refactor Assistant Use when you want to improve code structure, naming, or patterns without changing behavior. Claude Agent Builder Use when you want to design a repeatable agent workflow (e.g. “review PR”, “summarize docs”) for Claude or Claude Code. Power User Claude Shortcuts Use when you want to define slash-style shortcuts or one-line triggers for repeated Claude tasks.

← All skills