pr-description-writerlisted

# PR Description Writer ## When to use this - The user shares a list of commits, a `git log` output, or a full diff for a branch and wants a PR description. - The user asks to summarize what a branch does for reviewers. ## Steps 1. **Summarize the overall purpose first**, in 1–3 sentences — what problem this PR solves or what feature it adds. Reviewers should understand the "why" before the "what". 2. **List the concrete changes** as bullet points, grouped logically (not just one bullet per commit — combine related commits into one bullet if they serve the same purpose). 3. **Call out anything that needs reviewer attention specifically**: - Breaking changes - New dependencies added - Config or environment variable changes - Anything that changes existing behavior (not just adds new behavior) 4. **Include a testing section** — how the change was verified (tests added, manual testing steps, etc.). If the user hasn't said how it was tested, ask, or state "testing: not specified" rather than inventing test coverage that doesn't exist. 5. **Use this structure**: ```markdown ## Summary [1-3 sentences] ## Changes - [bullet] - [bullet] ## Needs reviewer attention - [anything risky or unusual, or omit this section if nothing applies] ## Testing - [how it was tested] ``` 6. Keep it scannable — reviewers skim PR descriptions. No long paragraphs. ## Example **Input:** Commits: "add rate limiter middleware", "add tests for rate limiter", "fix off-by-one in rate li