Use when opening a pull request or writing/rewriting its description – turn a branch's git diff and commit log into a clear, reviewer-friendly PR writeup with what/why/how, breaking changes, risk, testing, rollback, and where reviewers should focus.
Use when opening a pull request or writing/rewriting its description - turn a branch's git diff and commit log into a clear, reviewer-friendly PR writeup with what/why/how, breaking changes, risk, testing, rollback, and where reviewers should focus. Honest about gaps; no filler.This is the skill's description: the text your AI reads to decide when the skill applies.
devops-pr-describe/SKILL.md
---
name: pr-describe
description: Use when opening a pull request or writing/rewriting its description — turn a branch's git diff and commit log into a clear, reviewer-friendly PR writeup with what/why/how, breaking changes, risk, testing, rollback, and where reviewers should focus. Honest about gaps; no filler.
---
# pr-describe
Turn a branch of changes into a PR description a reviewer can actually act on.
The job is not to restate the diff — the reviewer can read the diff. The job is to
supply the **context the diff can't carry**: why this change exists, what could go
wrong, how it was verified, and where to look first. A good description is the
single highest-leverage thing you can do to get a fast, correct review.
## When to use
- Opening a PR / MR and you need a description
- An existing PR has a thin or stale description ("update stuff", "fix bug") and you
want to rewrite it from the actual changes
- A reviewer asked "what is this even doing / why?"
**When *not* to use:** a one-line trivial change where the title says it all (typo,
version bump) — a heavy template there is noise. And don't use this to *generate* a
diff or write code; it describes work that already exists.
## Gather the evidence first… load the full skill through Skill Me