Agent skill

PR Description Live

by mohitagw15856 in mohitagw15856/pm-claude-skills

Write a PR description grounded in the REAL diff — read the branch's actual changes via the GitHub connector, not a template the user fills in.

MITAuto-check passedDevelopment

Install PR Description Live

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

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

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills pr-description-live --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-live .claude/skills/pr-description-live && 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-live
GitHub stars
1.4k
Token cost
~1.1k tokens
SKILL.md length
570 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Write a PR description grounded in the REAL diff — read the branch's actual changes via the GitHub connector, not a template the user fills in.

  • Works in 5 steps: Summary — what this PR does and why, in… → Changes, grouped — by area/feature, not… → Testing — what was run/added and what a… → …
  • Asked to write my PR description
  • SKILL.md covers What This Skill Produces, Required Inputs, Framework: A Description a… and Execution (Cowork), plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

PR Description Live is an agent skill from mohitagw15856/pm-claude-skills. Write a PR description grounded in the REAL diff — read the branch's actual changes via the GitHub connector, not a template the user fills in. Use when asked to write my PR description, describe this pull request, draft the PR body from my branch, or document these changes in Cowork. Reads the commits and diff via the GitHub connector, derives what changed and why from the code itself, and produces a PR-description artifact (summary, changes, testing, risk) ready to paste — matching the repo's PR template if one…

Its SKILL.md is about 1.1k 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. It works with GitHub. 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 my PR description
  • Describe this pull request
  • Draft the PR body from my branch
  • Document these changes in Cowork

Example prompts

  • “/pr-description-live”

Workflow steps

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

  1. Summary — what this PR does and why, in two or three lines.
  2. Changes, grouped — by area/feature, not a raw file list; each with its purpose.
  3. Testing — what was run/added and what a reviewer should verify.
  4. Risk & rollout — what could break, migrations, flags, and how to back out.
  5. Reviewer's attention — the load-bearing change to look at first.

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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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 Live loads about 1.1k tokens when it runs. Until then it costs about 137 tokens; SKILL.md has 570 words of instructions outside code blocks.

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

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). 570 words, ~1,093 tokens.

Download SKILL.mdSave it as .claude/skills/pr-description-live/SKILL.md (or your agent's skills folder).
name
pr-description-live
description
Write a PR description grounded in the REAL diff — read the branch's actual changes via the GitHub connector, not a template the user fills in. Use when asked to write my PR description, describe this pull request, draft the PR body from my branch, or document these changes in Cowork. Reads the commits and diff via the GitHub connector, derives what changed and why from the code itself, and produces a PR-description artifact (summary, changes, testing, risk) ready to paste — matching the repo's PR template if one exists.

PR Description (Live)

A good PR description is written from the diff, not from memory — memory forgets the file you touched at 2am. In Claude Cowork this skill reads the actual changes on the branch and writes the description grounded in them, so the reviewer gets an accurate map of what moved and why.

Not quite this? Use pr-description-writer when you will paste the diff yourself instead of connecting GitHub.

What This Skill Produces

  • The PR description — summary, the changes grouped by area, how it was tested, and the risk/rollout — all derived from the real diff
  • Template-matched output — if the repo has a PR template, the body fills its sections; otherwise a clean default
  • The reviewer's map — the one or two files/decisions that deserve the closest look

Required Inputs

Ask for these if not provided:

  • The branch/PR — the branch name or PR number, and the base it targets
  • The why — the issue/ticket or one line of intent (the diff shows what, not always why)
  • Audience — internal team vs open-source contributors — tone and detail follow

Framework: A Description a Reviewer Trusts

  1. Summary — what this PR does and why, in two or three lines.
  2. Changes, grouped — by area/feature, not a raw file list; each with its purpose.
  3. Testing — what was run/added and what a reviewer should verify.
  4. Risk & rollout — what could break, migrations, flags, and how to back out.
  5. Reviewer's attention — the load-bearing change to look at first.

Execution (Cowork)

  1. Read the diff — via the GitHub connector, fetch the branch's commits and the full diff against base. Read the actual changes, not just commit messages.
  2. Derive the story — from the diff, work out what changed by area and infer intent; combine with the user's stated why. Flag anything the diff does that the stated intent doesn't explain.
  3. Match the template — check for .github/pull_request_template.md; if present, fill its sections; else use the default structure above.
  4. Write the description — grounded in the diff, no invented changes; call out migrations, new deps, and breaking changes found in the code.
  5. Emit the artifact — the ready-to-paste body; offer to set it on the PR via the connector, but only on request.

Guardrails: describe only what the diff actually contains — never list a change that isn't there; surface diff-vs-intent mismatches instead of hiding them; don't push/update the PR without explicit approval; if the connector is unauthorised, work from a pasted diff and say the branch couldn't be read.

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

Output Format

A PR Description (or the repo template, filled):

Summary

what & why — 2–3 lines

Changes
  • [area] — what changed and why
Testing
  • what was run/added · what the reviewer should verify
Risk & rollout
  • breaking changes / migrations / flags / back-out
Look here first
  • [file/decision] — why it's load-bearing

Quality Checks

  • Every listed change appears in the actual diff
  • Changes the diff makes that intent didn't explain are flagged
  • Migrations / new deps / breaking changes from the code are called out
  • The repo's PR template is used when present
  • Nothing was pushed to the PR without approval

Anti-Patterns

  • Describing intended changes that aren't in the diff.
  • A raw file list instead of grouped, purposeful changes.
  • Ignoring the repo's PR template.
  • Silently updating the PR without being asked.

Example Trigger Phrases

  • "Write the PR description from my branch in Cowork."
  • "Describe this pull request from the actual diff."
  • "Draft the PR body against main and match our template."
  • "Document these changes for reviewers — read the diff first."

© 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

Just SKILL.md in skills/pr-description-live of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

PR Description Live 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 Live compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR Description Live this skillmohitagw15856/pm-claude-skills1.4k—~1.1kAutomated 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
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
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

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

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k 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 Live

What does PR Description Live do?

Write a PR description grounded in the REAL diff — read the branch's actual changes via the GitHub connector, not a template the user fills in. PR Description Live is an agent skill from mohitagw15856/pm-claude-skills. Write a PR description grounded in the REAL diff — read the branch's actual changes via the GitHub connector, not a template the user fills in.

When should I use PR Description Live?

PR Description Live fits situations like: asked to write my PR description; describe this pull request; draft the PR body from my branch; document these changes in Cowork.

How do I install PR Description Live in Claude Code?

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

How do I install PR Description Live in Codex?

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

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

What does PR Description Live need to run?

SKILL.md names no scripts, command-line tools or credentials: PR Description Live is instructions for the agent only.

Does PR Description Live access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

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

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

About 1.1k tokens (SKILL.md is roughly 4.4k 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 Live?

Skills that share tags, products or a category with PR Description Live: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k 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 Live?

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.