PR Description

Write a pull request title and description from the actual diff and commits, with what changed, why, how it was tested and what to review. Use when asked to write or improve a PR description.

Git & Code Review Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add agentkitco/agentkit-dev-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add agentkitco/agentkit-dev-skills --skill pr-description
Manual install
git clone --depth 1 https://github.com/agentkitco/agentkit-dev-skills.git /tmp/agentkit-dev-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agentkit-dev-skills/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

# Write a PR description a reviewer can use

Goal: let a reviewer decide in two minutes what to look at, and let a future reader understand why the change exists.

## Gather

1. Find the base branch and run `git log --oneline <base>..HEAD` and `git diff --stat <base>...HEAD`, then read the diff.
2. Look for the reason: linked issue or ticket number in commits or branch name, the user's request, comments added in the diff. If the reason is not in any of these, ask the user; do not invent a motivation.
3. Check what was tested: test files in the diff, and commands the user ran. If tests were not run, say so plainly.
4. Look for a `.github/pull_request_template.md` or `PULL_REQUEST_TEMPLATE`. If one exists, fill it in instead of using the structure below.

## Structure

```
<Title: imperative, under 70 characters, names the behavior change, not the files>

## Why
<The problem or request, in 1 to 3 sentences. Link the issue if there is one.>

## What changed
- <Behavior-level bullets grouped by area, not a file list.>

## How to review
- Start with <file or area>; the rest follows from it.
- Risky part: <the part most likely to be wrong, and why>.
- Not changed on purpose: <anything a reviewer may expect and will not find>.

## Testing
- <Exact commands run and results.>
- <Manual steps and what was seen. "Not tested: ..." if applicable.>

## Rollout / risk
<Migrations, config, feature flags, compatibility, how to roll back. "None" only if true.>
```

## Rules
Read the full skill on GitHub

Details

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

FAQ

What does the PR Description skill do?

Write a pull request title and description from the actual diff and commits, with what changed, why, how it was tested and what to review. Use when asked to write or improve a PR description.

How do I install the PR Description skill?

Claude Code plugin: /plugin marketplace add agentkitco/agentkit-dev-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Related skills

Agents Md Audit

agentkitco/agentkit-dev-skills

Audit an AGENTS.md, CLAUDE.md, Cursor rule or Copilot instructions file for stale commands, broken paths, vague rules, secrets and contradictions. Use to review or trim agent instructions.

AI, LLMs & AgentsIn 1 list

Brag Doc From Git

agentkitco/agentkit-dev-skills

Build an evidence-based brag doc or self-review draft from your merged PRs and commits, leaving visible gaps where results are unknown. Use for review season, promotion cases or resumes.

Git & Code ReviewIn 1 list

Dependency Upgrade

agentkitco/agentkit-dev-skills

Upgrade one dependency at a time by reading its changelog, planning for breaking changes, updating code and proving it still builds and passes. Use to bump, update or migrate a package.

Git & Code ReviewIn 1 list

Review My Diff

agentkitco/agentkit-dev-skills

Self-review uncommitted or branch changes before a PR, with findings ranked by severity and backed by file and line evidence. Use when asked to review my changes or check my diff.

Git & Code ReviewIn 1 list

Report

danybgoode/golden-frijoles

Posts a project report to a chat destination, at the cadence asked for. Daily: a delta-only standup of overnight signals across every repo the project spans (opened/merged PRs and CI, the latest browser smoke, BUILD-ORDER drift, open-PR state, stale previews). Weekly: an executive recap/retro (merged PRs, shipped epics, deploys per app repo, a retro digest). PMO: the weekly operational report with scrum/DORA/doc-ops metrics and a story deck, or the on-demand monthly stakeholder packet with a metrics sheet. Use when the product owner asks to "post the standup", "run the daily standup", "what ha

Git & Code ReviewIn 1 list

Build Order Sync

danybgoode/golden-frijoles

Regenerates Roadmap/00-ideas/BUILD-ORDER.md when it has drifted from the SSOT (each epic README's frontmatter status:) and opens a claude/ docs PR with the fix — never hand-edits the board. Use when the product owner asks to "sync the build order", "regenerate BUILD-ORDER.md", "check board drift", "is the build-order board stale", "open a build-order PR", or as the nightly ops routine's first step. Runs scripts/build-order-sync.mjs, which does the check, the regen, and (on real drift) the branch/commit/ push/PR — this skill just invokes it and reports the result.

Git & Code ReviewIn 1 list

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