write-pr-description

TL;DR

Warp's guide to PR descriptions, built on one idea: give the reviewer what the diff can't. The agent first gathers the motivation, the linked issue or spec, real decisions, the blast radius and the validation, from git log and diff or from gh for a PR number, and verifies claims by looking, such as reading what the change deletes or grepping a flag before saying it's on. A repo's PR template is followed, its own instructions first: headings stay as written, every section gets an answer, even a one-clause no, boxes are ticked only when true, and machine-read markers are kept. Without a template it writes an opening paragraph, then a review guide when needed, What changed and Validation, dropping sections on small changes. Validation is reported honestly: nothing ran, CI will show it, tests added but unrun, or it couldn't be run, never intent written as a result. Prose follows ASD-STE100 Simplified Technical English. The cut pass removes what the diff already shows, test inventories, explanations of standard tools and anything said twice, but keeps decisions and open questions. A self-check and a list of anti-patterns, such as narrating the branch's history or grading your own work, close it.

Summarizes the skill at 8792394.