pr-description-writer
Installation
SKILL.md
PR Description Writer
A PR description exists so the reviewer can decide how hard to look, where to
look, and whether the merge can be undone. Most descriptions fail all three:
they narrate the commits, assert "tested, works", and call the change "low
risk" while it ships a DROP COLUMN. This skill writes the body in five
sections (summary, why, evidence, how to verify, merge risk), classifies the
change from its real file list and diff, and lints the result so an honest
classification is enforced rather than hoped for.
This skill is for the author. Reviewing someone else's PR (blast-radius
analysis, security scanning, coverage deltas) is a separate job covered by the
engineering/pr-review-expert package; this one only produces and checks the
description.