Individual skill

pr-description-live

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.

skills/pr-description-live/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,539
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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
Back to top