writing-pr-descriptions

PR descriptions should follow your project's voice rules for tone and brevity. This skill generates descriptions that adhere to your project's conventions, sourcing your PR template and embedding guidance on audience, anti-patterns, and workflow to ensure consistency across all contributions.

Effective PR descriptions combine what changed, why it matters to users, and validation steps. This skill drafts sectioned bodies that highlight user impact, include screen-recording references or links to Jira/Slack, and outline how to validate the changes before submission.

Yes. This skill provides starter templates for common PR types and validation workflows. Templates establish consistent structure across your project while the skill generates descriptions tailored to your specific changes and voice guidelines.

Anti-pattern guidance built into this skill highlights what not to do—vague impact claims, missing validation steps, or tone misalignment. It generates descriptions that steer clear of these pitfalls while conforming to your project's workflow conventions.

Yes. This skill applies to PR creation via gh CLI and editing existing pull requests. It gathers your changes and drafts descriptions that fit your project's workflow, whether you're composing new PRs or refining submitted ones.