What problem does it solve? Pull request descriptions are often vague, missing verification evidence, or lacking risk context, which slows down code review and lets unverified claims slip through. This Skill produces reviewer-ready PR titles and bodies grounded in the actual diff and the commands that were really run. ## Core Features & Use Cases - Semantic Titles: Generates CI-compliant type(scope): imperative subject titles using the exact accepted types (feat, fix, chore, docs, refactor, test, ci, perf). - Structured Body Sections: Enforces Summary with exact diff statistics, What Changed, Architecture, Testing, What's NOT Changed, and a P0-P3 Risk Analysis with a summary table. - Verification Discipline: Requires exact test commands and results from git diff --stat, vitest, tsc, lint, and Playwright runs, forbidding invented metrics or unverified claims. - Use Case: After finishing a feature branch, ask for a PR description and receive a complete title and body with real diff numbers, the tests actually executed, and a risk mapping reviewers can act on. ## Quick Start Write a pull request title and body for my current branch changes following the pr-description skill.