pr-description

pr-description is a skill for Claude Code from davila7/claude-with-skills. It costs 37 tokens per session (367 once invoked), scanned A, original, MIT.

A writing aid for pull requests, which are proposed code changes submitted for review. It creates a description covering the changes, the reason for them, and how to test them.

In plain words
What is it for?
Use it when opening or preparing a pull request to summarize commits, explain the motivation, provide review steps, and record relevant notes.
Why use it?
It gives reviewers the context they need without making you assemble the description from git history and file changes yourself.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it when opening or preparing a pull request to summarize commits, explain the motivation, provide review steps, and record relevant notes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/davila7/claude-with-skills/pr-description
About the project

Claude With Skills is a progressive course that teaches developers to create reusable, portable Agent Skills for Claude Code, from basic SKILL.md files to advanced automation and plugin packaging. It is intended for developers who want repeatable instructions and workflows instead of repeatedly pasting the same guidance. The catalogue contains the course's skills, agents, and instruction.

davila7/claude-with-skills · 12 stars · on GitHub · claude-with-skills.vercel.app

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add davila7/claude-with-skills --skill pr-description
Clone the repo
git clone --depth 1 https://github.com/davila7/claude-with-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for pr-description

README.md
[![agentmods](https://agentmods.dev/badge/skills/davila7/claude-with-skills/pr-description/github.svg)](https://agentmods.dev/skills/davila7/claude-with-skills/pr-description)
Your own site
<a href="https://agentmods.dev/skills/davila7/claude-with-skills/pr-description"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/pr-description/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for pr-description

Your own site · 80×15
<a href="https://agentmods.dev/skills/davila7/claude-with-skills/pr-description"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/pr-description.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 367 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.00367
Opus 5 $0.00018 $0.00183
Sonnet 5 $0.00007 $0.00073
Haiku 4.5 $0.00004 $0.00037

Measured 12d ago against content hash 3d4144bb4a81, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

pr-description scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

src/content/docs/01-basic/lesson-03-repetitive-tasks/examples/pr-description/SKILL.md · 59 lines

What it actually says

Instructions

  1. List the commits on this branch:

    git log --oneline main..HEAD
    

    If main does not exist, try master:

    git log --oneline master..HEAD
    
  2. Get a summary of changed files:

    git diff main...HEAD --stat
    

    (Use master...HEAD if main does not exist.)

  3. Write a PR description using the following structure. Output only the description, with no surrounding explanation.


Summary

  • What changed, as a bullet list. One bullet per logical change. Focus on the user-visible or caller-visible effect, not the implementation detail.

Motivation

A short paragraph (two to four sentences) explaining the problem being solved. Why does this PR need to exist? What was wrong or missing before?

Test plan

A checklist of specific steps a reviewer can follow to verify the change works:

  • Step one
  • Step two
  • Edge case or error scenario to check

Notes

Anything a reviewer should know that is not obvious from the diff: migrations that need to run, environment variables that need to be set, follow-up work that is intentionally deferred, known limitations.

If there are no reviewer notes, omit this section entirely.


Keep the description factual and concise. Do not pad with filler phrases. If the PR is straightforward, the description should be short.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 59 lines · 37 tokens per session scan A 3d4144bb4a81

Subscribe to this mod's changes

pr-description is a skill published in the GitHub repository davila7/claude-with-skills (12 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 367 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

changelog-composer

Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".

Mathews-Tom/armory · 67 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens