What problem does it solve?
Poorly written pull request descriptions leave reviewers without critical context about code changes, lead to unnecessary back-and-forth during review, and increase the risk of merging faulty code due to missing validation or rollback information. This Skill solves that by guiding you to create structured, complete PR descriptions that provide all the context reviewers need to efficiently approve changes.
Core Features & Use Cases
- Structured Template Enforcement: Automatically ensures all required sections (linked issues, background, changes, validation, risk, rollback) are included in every PR description, so no critical information is omitted.
- Quality Guardrails: Prevents vague descriptions, requires reproducible validation steps with paired commands and results, and mandates explicit risk and rollback details for delivery-focused changes.
- Use Case: When submitting a code change to a team repository, use this Skill to generate a PR description that lets reviewers quickly understand the purpose of the change, how it was tested, and how to revert it if issues arise, cutting down review time and reducing merge risks.
Quick Start
Use the pr-writer skill to generate a complete, review-ready pull request description for your latest code changes, including all required context for your team's reviewers.