PR Description

Write or update a GitHub PR description a teammate understands in one quick read: clear before/after behavior, useful visual evidence, and plain sentences grounded in the diff and real verification. Use when opening a PR or editing its description.

49 stars 10 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add petekp/claude-code-setup --skill pr-description
Manual install
git clone --depth 1 https://github.com/petekp/claude-code-setup.git /tmp/claude-code-setup
mkdir -p ~/.claude/skills
cp -r /tmp/claude-code-setup/skills/pr-description ~/.claude/skills/pr-description

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# PR description

Write for a teammate who knows the product, hasn't followed the work, and is reading between other tasks. After one quick read they should know what changed and what to check. A dense description goes unread even when it's accurate.

## Establish the behavior before drafting

Read the diff and its affected callers. Compare the base and head behavior before choosing the summary. For a change spanning several types, roles, states or delivery channels, identify the relevant cases and establish each one's before and after. Separate stored data from what people see, and distinguish surfaces such as an in-app pop-up and a desktop notification.

Include unchanged cases when readers could reasonably assume they changed. For a rule that selects cases, check its exceptions and its default for unrecognized cases. Group cases only when their baseline, outcome and conditions match; name the members when a broad label would hide the scope.

This comparison is preparation, not a required published inventory or separate artifact. Investigate the affected behavior, not the whole system. Mark unknowns and distinguish source inspection from observed behavior. Don't invent motivation or claim verification you haven't done.

## Picture first

Include a picture when it makes the change easier to assess than the text or diff alone. Put it above the first heading.
Read the full skill on GitHub

Details

Skill name
pr-description
Path
skills/pr-description/SKILL.md
License
MIT
Repo updated
26 October 2026

FAQ

What does the PR Description skill do?

Write or update a GitHub PR description a teammate understands in one quick read: clear before/after behavior, useful visual evidence, and plain sentences grounded in the diff and real verification. Use when opening a PR or editing its description.

How do I install the PR Description skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add petekp/claude-code-setup --skill pr-description. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is PR Description popular?

It lives in petekp/claude-code-setup, which has 49 GitHub stars and 10 forks.

Related skills

Catch Up

49

petekp/claude-code-setup

Give the human a fast, plain-English catch-up on what changed in the project: what the agents did, why, and what decisions need their input. Use when the user asks to "catch me up", "what changed", "where are we", "recap", "brief me", "give me the rundown", "what did you do", "summarize the session", or "fill me in", or otherwise wants to get back up to speed after being away.

AI, LLMs & Agents10

Clean Copy

49

petekp/claude-code-setup

Cut interface copy that should not exist. Captions that restate a label, hints that pre-empt a worry the user never had, warnings that are scar tissue from a fixed bug. Use when writing or reviewing any user-facing string (labels, hints, empty states, toasts, confirmations, button text), or when asked to clean up or tighten copy.

Writing & Content10

Code Comments

49

petekp/claude-code-setup

Write, review, or remove code comments. Use when adding comments or doc comments, reviewing the comments in a diff, or cleaning up or removing comments.

Software Development10

PR Screenshot Comparison

49

petekp/claude-code-setup

Create clear, polished before-and-after screenshots from the actual running product for a GitHub pull request. Use when a UI change needs visual proof: capture matching product states, crop to the relevant UI, stitch and caption one comparison image, attach it natively to the PR, and keep the image out of the repository.

Git & Code Review10

Git Workflow

43

jefflester/claude-skills-supercharged

Git workflow best practices including commit messages, branching strategies, pull requests, and collaboration patterns. Use when working with Git version control.

Git & Code Review

PR Self Review

49

petekp/claude-code-setup

Draft explanatory author-context comments for the user's own PR or local diff. Use for self-review or reviewer context, not a formal review submission. Posting requires approval.

Git & Code Review10

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.