pr-description-writer

# PR Description Writer ## What this skill does This skill directs the agent to read a diff or a plain summary of changes and produce a complete, well-structured pull request description. It covers what changed, why it changed, how reviewers can test it, and what edge cases or risks to be aware of — so reviewers can do their job without having to chase you for context. Use this when you're about to open a PR and want a description that will actually get reviewed instead of skipped, or when you need to document a large change for future reference. ## How to use ### Claude Code / Cline Copy this file to `.agents/skills/pr-description-writer/SKILL.md` in your project root. Then ask: - *"Write a PR description for these changes using the PR Description Writer skill."* - *"Use the PR Description Writer skill. Here's the diff."* You can provide: - A `git diff main...HEAD` or `git diff` output - A bullet list of what changed (if the diff is too large to paste) - The GitHub issue number this PR closes (optional) - Any context about why the change was needed ### Cursor / Codex Paste the instructions from the section below into your session, then provide your diff or change summary. ## The Prompt / Instructions for the Agent When asked to write a pull request description, follow these steps: ### 1. Understand the change Read the diff or change list and identify: - What files / modules were touched? - Is this a new feature, a bug fix, a refactor, a performance improvement,...