New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

PR Description Writer

by mohitagw15856 in mohitagw15856/pm-claude-skills

Write a clear, structured pull request description from a git diff, branch summary, or commit list.

MITAuto-check passedDevelopment

Install PR Description Writer

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill pr-description-writer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills pr-description-writer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pr-description-writer .claude/skills/pr-description-writer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pr-description-writer
GitHub stars
1.4k
Token cost
~1.6k tokens
SKILL.md length
843 words
Files
4 (incl. references)
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Write a clear, structured pull request description from a git diff, branch summary, or commit list.

  • Works in 4 steps: [Setup step if needed] → [Action to take] → [What to verify] → …
  • Asked to write a PR description
  • SKILL.md covers Required Inputs, Output Format, Deeper Materials and Scoring Rubric (0–40), plus 3 more sections
  • Calls git

What it does

PR Description Writer is an agent skill from mohitagw15856/pm-claude-skills. Write a clear, structured pull request description from a git diff, branch summary, or commit list. Use when asked to write a PR description, draft a pull request, or document code changes. Produces a description with summary, motivation, changes made, testing steps, and reviewer guidance.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/reviewer-empathy.md`, `references/worked-example.md` and `templates/pr-template.md`).

It sits in Development, covering Pull requests. It works with Git. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked to write a PR description
  • Draft a pull request
  • Document code changes

Example prompts

  • “/pr-description-writer”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. [Setup step if needed]
  2. [Action to take]
  3. [What to verify]
  4. [Edge case to check]

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

PR Description Writer loads about 1.6k tokens when it runs, and up to ~4k if it reads all its reference files. Until then it costs about 78 tokens; SKILL.md has 843 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~78
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 843 words, ~1,563 tokens.

Download SKILL.mdSave it as .claude/skills/pr-description-writer/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
pr-description-writer
description
Write a clear, structured pull request description from a git diff, branch summary, or commit list. Use when asked to write a PR description, draft a pull request, or document code changes. Produces a description with summary, motivation, changes made, testing steps, and reviewer guidance.
deprecated
2026-08-21
supersededBy
pr-description

PR Description Writer Skill

Writes structured, reviewer-friendly pull request descriptions from a diff, commit list, or informal notes. Covers the what, why, and how-to-review so reviewers can start immediately.

Not quite this? Use pr-description-live when you want it to read the real diff through the GitHub connector.

Required Inputs

Ask for these if not provided:

  • What changed (paste a git diff, git log --oneline, or describe the changes in plain English)
  • Why it was changed (the problem being solved or feature being added)
  • How to test it (any specific steps a reviewer needs to verify it works)
  • Risk level (low / medium / high — affects how much reviewer guidance to include)
  • PR type (feature / bug fix / refactor / dependency upgrade / config change / hotfix)
  • Target branch (e.g. main / develop / release/2.4 — affects risk framing and reviewer guidance)
  • Linked issue or ticket (e.g. JIRA-1234, GitHub #567 — or "none")

Output Format

Title

A clear, imperative-mood title under 72 characters: [type]: [concise description of what changed]

Examples:

  • feat: add rate limiting to the public API
  • fix: resolve race condition in session expiry
  • refactor: extract payment logic into PaymentService
Summary

2–3 sentences covering:

  • What this PR does (the change)
  • Why it was needed (the problem or goal)
  • The approach taken (at a high level)
Changes Made

Bullet list of specific changes — one bullet per logical change, not per file:

  • Added [X] to handle [Y]
  • Refactored [A] to reduce [B]
  • Removed [C] as it was replaced by [D]
  • Updated [E] to fix [F]
Screenshots / Demo

[If UI change: include before/after screenshots or a screen recording] [If API change: include example request/response] [If no visual change and no API contract change: omit this section entirely — do not leave it as a placeholder]

How to Test

Step-by-step instructions a reviewer can follow:

  1. [Setup step if needed]
  2. [Action to take]
  3. [What to verify]
  4. [Edge case to check]

Include any specific commands, test data, or environment flags needed.

Testing Checklist
  • Unit tests added/updated
  • Integration tests added/updated
  • Edge cases covered
  • Manual testing completed
  • No regressions in existing tests
Reviewer Notes

Flag anything that warrants extra attention:

  • Areas of uncertainty where a second opinion is welcome
  • Deliberate trade-offs made (and why)
  • Out-of-scope items noticed but not addressed
  • Dependencies on other PRs (link them)
  • Closes #[issue number] (if applicable)
  • Related to #[PR/issue number]

Deeper Materials

This skill ships with support files — use them when they are available:

  • references/reviewer-empathy.md — PR Descriptions as Review Navigation. Apply it while producing the output; it carries the calibration and judgment calls the method summary above compresses.
  • templates/pr-template.md — a fill-in version of the deliverable with the quality gates inline. Offer it when the user wants to work the document themselves rather than have it generated.
Show full SKILL.md (396 more words)Show less

Scoring Rubric (0–40)

Score any output of this skill before handing it over; 32+ is ship-quality.

Dimension0510
Why over whatDescription only restates the diff; no motivation givenThe what is clear, but the why is thin or generic ("improves the code")Problem, goal, and approach are explicit; the description adds context the diff cannot convey
Title & structureSingle unstructured paragraph; title vague, missing a type prefix, or over 72 charactersStructured with headers, but the title or section usage slips (placeholder sections left in)Valid type prefix, imperative mood, under 72 characters; sections let a reviewer navigate straight to what they need
Testing reproducibilityNo testing stepsSteps exist but assume codebase familiarity or skip edge casesSomeone unfamiliar with the code can reproduce verification — commands, test data, flags, and at least one edge case included
Risk-calibrated reviewer guidanceHigh-risk PR with no reviewer notes, or notes that are pure boilerplateNotes exist but name no specific trade-off, uncertainty, or out-of-scope itemGuidance matches risk: high-risk flags specific concerns and deliberate trade-offs; low-risk keeps notes to one line or omits them

Quality Checks

  • Title is imperative mood and under 72 characters
  • Summary explains what AND why (not just what)
  • Changes list describes logical changes (not file-by-file changes)
  • Title starts with a valid type prefix (feat / fix / refactor / chore / deps / config / hotfix) and is under 72 characters
  • Testing steps are reproducible by someone unfamiliar with the code
  • For high-risk PRs, Reviewer Notes flags at least one specific area of concern or deliberate trade-off; for low-risk PRs, Reviewer Notes is either omitted or kept to one line

Anti-Patterns

  • Do not write a description that only restates what changed — explain why the change was made
  • Do not skip the testing steps — reviewers need to know how to verify the change works
  • Do not omit the reviewer notes for high-risk PRs — flag deliberate trade-offs and areas needing careful review
  • Do not describe implementation details that are obvious from the diff — add context that the diff cannot convey
  • Do not produce a single paragraph — structure with headers so reviewers can navigate to what they need

Usage Examples

  • "Write a PR description for these changes" + [paste diff or description]
  • "Draft a pull request for [feature]"
  • "I need a PR description — here's what I changed"
  • "Summarise these commits into a PR description"
  • "Write the PR body for this branch"

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/pr-description-writer of mohitagw15856/pm-claude-skills.

  • SKILL.md
  • references/reviewer-empathy.md
  • references/worked-example.md
  • templates/pr-template.md

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

PR Description Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

PR Description Writer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR Description Writer this skillmohitagw15856/pm-claude-skills1.4k—~1.6kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Open Code Review CLIalibaba/open-code-review46k—~3.1kAutomated safety check: PassApache-2.0
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Open Code Review CLI

    alibaba/open-code-review

    Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.

    46k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo

  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about PR Description Writer

What does PR Description Writer do?

Write a clear, structured pull request description from a git diff, branch summary, or commit list. PR Description Writer is an agent skill from mohitagw15856/pm-claude-skills. Write a clear, structured pull request description from a git diff, branch summary, or commit list.

When should I use PR Description Writer?

PR Description Writer fits situations like: asked to write a PR description; draft a pull request; document code changes.

How do I install PR Description Writer in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill pr-description-writer -a claude-code`. Or copy the skill folder (skills/pr-description-writer in mohitagw15856/pm-claude-skills) into .claude/skills/pr-description-writer in your project. Claude Code loads it when a task matches its description.

How do I install PR Description Writer in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill pr-description-writer -a codex`. Or copy the skill folder (skills/pr-description-writer in mohitagw15856/pm-claude-skills) into .agents/skills/pr-description-writer in your project. Codex loads it when a task matches its description.

Can I use PR Description Writer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill pr-description-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-description-writer, .gemini/skills/pr-description-writer, .github/skills/pr-description-writer and .opencode/skills/pr-description-writer in your project.

What does PR Description Writer need to run?

Going by SKILL.md and its folder, PR Description Writer needs the command-line tools its instructions call (git).

Does PR Description Writer access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is PR Description Writer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does PR Description Writer use?

PR Description Writer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does PR Description Writer use?

About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.4k tokens, read only when the agent opens those files.

What are the alternatives to PR Description Writer?

Skills that share tags, products or a category with PR Description Writer: Finishing a Development Branch (obra/superpowers, 297k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Open Code Review CLI (alibaba/open-code-review, 46k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR Description Writer?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.