Write a pull request body a reviewer can predict the diff from, scaled to the size of the change.

GPL-3.0Auto-check passedDevelopment

Install PR Description

skills CLI
$ npx skills add deadlock-mod-manager/deadlock-mod-manager --skill pr-description -a claude-code

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

GitHub CLI
$ gh skill install deadlock-mod-manager/deadlock-mod-manager pr-description --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/deadlock-mod-manager/deadlock-mod-manager.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pr-description .claude/skills/pr-description && 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
GitHub stars
574
Token cost
~962 tokens
SKILL.md length
546 words
Files
1
Skills in repo
25
Repo updated
First seen
Licence
GPL-3.0

At a glance

Write a pull request body a reviewer can predict the diff from, scaled to the size of the change.

  • Filling in a PR description
  • SKILL.md covers When to use, Scale, How to write it and Title, plus 1 more section
  • Calls npx and git
  • Tasks that involve Pull requests

What it does

PR Description is an agent skill from deadlock-mod-manager/deadlock-mod-manager. Write a pull request body a reviewer can predict the diff from, scaled to the size of the change. Use when creating, rewriting, or filling in a PR description.

Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. The repository describes itself as: A mod manager for the Valve game Deadlock. The licence is GPL-3.0.

When your agent uses it

  • Filling in a PR description
  • Tasks that involve Pull requests

Example prompts

  • “/pr-description”

Requirements

  • Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit 45c273c. 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:

    • npx
    • git

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

  • Network

    No URLs in SKILL.md. Its commands use npx and 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 loads about 962 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 546 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~962

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 deadlock-mod-manager/deadlock-mod-manager at commit 45c273c, republished under its GPL-3.0 licence (© deadlock-mod-manager). 546 words, ~962 tokens.

Download SKILL.mdSave it as .claude/skills/pr-description/SKILL.md (or your agent's skills folder).
name
pr-description
description
Write a pull request body a reviewer can predict the diff from, scaled to the size of the change. Use when creating, rewriting, or filling in a PR description.

PR Description

A reviewer reads the description before the diff. Write so they could predict the diff, and so a reader six months later understands why the change was needed.

Length follows the diff, not the effort. A long description on a small diff buries the one thing they needed.

When to use

  • Creating, rewriting, or filling in a pull request body.
  • The description has to stand on its own for review.

Scale

Start from the row that matches the change, then add a section only when its trigger fires.

ChangeBody
Copy, config, dependency bump, typoTicket line and one sentence. No headings.
Single concern, a handful of filesTicket line, 1–3 sentence summary, test plan.
Several independent changes, or non-obvious reasoningOne numbered section per change. A diagram only where it beats a sentence.

Add, at any size: a callstack when call flow changed, a before/after table when data outcomes changed, the artifact you looked at when you verified by looking, a follow-up ticket when something is left undone.

How to write it

Lead with the ticket. First line, before any heading, with a magic word (fixes, closes, refs) and a link. Name absorbed tickets and filed follow-ups here too. Skip the line only when the repo has no tracker and the change has no issue.

Explain the change, not the diff. The Files tab already has the diff. For a fix: which real scenario broke, why the old code looked correct, and why the new code is. For a feature: what was impossible before, and what the design commits to. When there are several changes, one sentence naming the shape they share comes before the numbered sections.

Be concrete. Real identifiers, values, and file names. Cut any sentence that does not change what the reviewer does: subsystem recaps, restating the diff, background the ticket already covers, self-justification, notes about your own process.

Show both states in one frame when a sentence cannot settle the mismatch. One fenced block, both sides labeled, the disagreeing line marked. If a sentence settles it, write the sentence.

Show full SKILL.md (200 more words)Show less

Number sections when there are several, and reference them from the test plan (§3) so each test defends a claim.

Callstack when who-calls-whom changed. Paste npx calldiff@latest diff output (see 095-calldiff.mdc) and narrate the + / - lines. Skip for copy, translations, CSS, config, and schema-only changes. A heading that only reports the tool found nothing is worse than no heading.

The test plan proves the change. Name each new test, map it to the section it defends, and say it failed without the change. List updated assertions as from/to. Name the suites that ran, and pre-existing failures that also fail on the base.

Predict data outcomes with one row per user-visible quantity, where the numbers came from, and how someone else confirms them after merge.

Attach the evidence. A screenshot, recording, or captured output belongs in the section it supports, with alt text that says what the reviewer is looking at. Collapse everything except the one artifact that is the point of the PR.

Title

The title becomes the squash commit. Follow git-conventions: type(scope): description, imperative, under 100 characters. Check recent git log --oneline when the repo's convention differs.

© deadlock-mod-manager, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/pr-description of deadlock-mod-manager/deadlock-mod-manager.

Open the folder on GitHubat commit 45c273c

Compare with similar skills

PR Description 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 compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR Description this skilldeadlock-mod-manager/deadlock-mod-manager574—~962Automated safety check: PassGPL-3.0
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT

Similar skills

  • 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.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k 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 starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

More from deadlock-mod-manager/deadlock-mod-manager

All 25 skills in this repo
  • Skill Creator

    deadlock-mod-manager/deadlock-mod-manager

    Create new agent skills following the Agent Skills specification.

    574 GitHub starsUsed in 1 repo~2.9k tokens
    Auto-check passed
  • Create Auth Skill

    deadlock-mod-manager/deadlock-mod-manager

    Scaffold and implement authentication in TypeScript/JavaScript apps using Better Auth.

    574 GitHub starsUsed in 4 repos~3.4k tokens
    Auto-check passed
  • Opensrc

    deadlock-mod-manager/deadlock-mod-manager

    Fetch source code for npm, PyPI, or crates.io packages and GitHub/GitLab repos to provide AI agents with implementation context beyond types and docs.

    574 GitHub stars~910 tokensUpdated today
    Auto-check passed
  • Security Review

    deadlock-mod-manager/deadlock-mod-manager

    Security code review for Tauri/Rust/TypeScript desktop apps and Hono/oRPC APIs.

    574 GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Babysit

    deadlock-mod-manager/deadlock-mod-manager

    Stay on one pull request until it is merge-ready, fixing the highest-priority blocker and telling the user when it is green.

    574 GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Changeset

    deadlock-mod-manager/deadlock-mod-manager

    Generate a changeset file describing the current PR's changes.

    574 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Categories

Questions about PR Description

What does PR Description do?

Write a pull request body a reviewer can predict the diff from, scaled to the size of the change. PR Description is an agent skill from deadlock-mod-manager/deadlock-mod-manager. Write a pull request body a reviewer can predict the diff from, scaled to the size of the change.

When should I use PR Description?

PR Description fits situations like: filling in a PR description; tasks that involve Pull requests.

How do I install PR Description in Claude Code?

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

How do I install PR Description in Codex?

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

Can I use PR Description 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 deadlock-mod-manager/deadlock-mod-manager --skill pr-description -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, .gemini/skills/pr-description, .github/skills/pr-description and .opencode/skills/pr-description in your project.

What does PR Description need to run?

Going by SKILL.md and its folder, PR Description needs the command-line tools its instructions call (npx and git). Our summary lists: Node.js.

Does PR Description access the network?

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

Is PR Description 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 use?

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

How many tokens does PR Description use?

About 962 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to PR Description?

Skills that share tags, products or a category with PR Description: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR Description?

deadlock-mod-manager (a GitHub organization) maintains it in deadlock-mod-manager/deadlock-mod-manager, which has 574 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 8, 2026.

Source: deadlock-mod-manager/deadlock-mod-manager on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.