Skill

pr-description

Renders standardized markdown PR description bodies with Why, What changed, Risk, and Test plan sections. Triggers on 'draft PR' phrases or before gh pr create/edit.

Git

Github

Markdown

git-workflow

documentation

npx claudepluginhub marcoskichel/empire --plugin empire-git

Tool Access

This skill is limited to using the following tools:

BashReadGlobGrep

Preview

IMPORTANT: Output the rendered description verbatim. Do not summarize, paraphrase, or describe this skill. The caller pipes your output to `gh pr create` or `gh pr edit` unchanged.

SKILL.md

Similar Skills

using-superpowers

185.1k

Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.

3 files

superpowers

Stats

Parent Repo Stars8

Parent Repo Forks0

Last CommitMay 5, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

PR Description Template

IMPORTANT: Output the rendered description verbatim. Do not summarize, paraphrase, or describe this skill. The caller pipes your output to gh pr create or gh pr edit unchanged.

Voice

Senior dev writing for peers. Direct. Active voice. Imperative mood.
No "this PR", "this commit", "I am", "we", filler openers.
Explain why and what users or callers experience differently. Cut anything obvious from the diff.
No emoji. No H1. No marketing tone. No "N/A" or "Risk: None".

Length

Diff size	Budget
≤ 100 LOC	≤ 80 words, drop Risk and Test plan unless non-trivial
≤ 500 LOC	≤ 200 words, include only non-empty sections
> 500 LOC	≤ 200 words, flag size in Risk, summarize at higher level

Skip empty sections entirely.

Sections

Render between markers. Preserve everything outside markers when updating.

<!-- pr-description:start -->
## Why
1–2 sentences. Problem or goal. Link issue if a commit references one.

## What changed
3–5 bullets. Behavior changes only — what users or callers experience differently.
Skip mechanical changes (renames, moves, test additions) unless they affect behavior.
Pick the most important changes; don't enumerate everything.

## Risk
Migrations, breaking API, new env vars or deps, rollback notes, perf concerns.
Only include if there's real risk. Prefix breaking changes with `BREAKING:`.

## Test plan
Manual steps to verify the change locally.
Omit for simple diffs or when the behavior is self-evident.
Never list CI steps (lint, typecheck, unit tests, CI pipelines).
<!-- pr-description:end -->

PR chains

When the branch was cut from another feature branch (not from main/master), or when the user provides a parent PR URL, add before the opening marker:

Depends on: <PR URL or branch name>

Detect by running git log --oneline <default-branch>..HEAD and checking if the branch base differs from the repo default branch.

Update mode

If an existing body is provided:

Replace only content between  and .
Preserve all content outside markers (screenshots, reviewer notes, Fixes #N, task lists, Depends on: lines).
If markers are absent: wrap new body in markers, append after author-written content.

Special cases

Formatting/whitespace only: single line Formatting only. No behavior change. between markers.
Title (when requested): Conventional Commits, lowercase, no period, ≤ 72 chars.
Body language matches the language of recent commit messages.

Anti-patterns

Bad	Good
"This PR adds support for…"	"Add support for…"
"We refactor auth to…"	"Refactor auth: extract token validation into…"
"Various fixes"	(list each)
"Fixes bug"	"Fix off-by-one in pagination cursor when total % limit == 0"
"Updated tests"	(omit — visible in diff)
"Renamed X to Y"	(omit unless rollout-relevant)
"Ran lint / CI / tests"	(never include in test plan)