PR Writer

Purpose

Write effective pull request descriptions — clear, structured, and reviewable — that communicate what changed, why it changed, and how it was validated. Good PR descriptions reduce review time, catch bugs earlier, and create an auditable project history.

Agent Protocol

Trigger

Exact user phrases: "write PR", "pull request", "PR description", "PR template", "create PR", "open a PR", "draft PR", "PR summary", "PR title", "write a pull request".

Input Context

• PR type (feature, bugfix, refactor, chore, docs, hotfix)
• Code changes (files changed, additions/deletions, key modifications)
• Issue or ticket reference (GitHub issue, JIRA, Linear)
• Testing done (unit, integration, manual, E2E)
• Dependencies or breaking changes
• Reviewer notes (areas of concern, decisions made)