Generates comprehensive, structured PR (Pull Request) descriptions by deeply analyzing the diff and codebase. Produces sections covering: issue being solved, impacted areas, data flow before/after the change, code quality score, architecture score, test coverage score, testing scenarios, and improvement suggestions. Use when the user asks to "generate a PR description", "write PR notes", "document this pull request", "create PR summary", or any variant of describing/documenting a code change for review.
Generate thorough, reviewer-friendly PR descriptions that surface the full context of a change.
Collect the following before writing anything:
git diff main...HEAD (or the appropriate base branch) to get all changed files and lines.git log main...HEAD --oneline for a summary of commits.#123, JIRA-456).If the diff is large (>500 lines), read changed files selectively - focus on entry points, interfaces, and core logic rather than generated or lock files.
Before writing, reason through:
Assign three integer scores (1-10) with brief rationale. See references/scoring-rubric.md for detailed criteria.
| Dimension | Score | Notes |
|---|---|---|
| Code Quality | x/10 | readability, DRY, error handling, naming |
| Architecture | x/10 | separation of concerns, coupling, extensibility |
| Test Coverage | x/10 | coverage breadth, edge cases, meaningful assertions |
Use the template in references/pr-template.md. Populate every section - do not leave placeholders.
After the description, append a Suggestions section listing concrete, actionable improvements you noticed in the diff that are out of scope for this PR. Prioritize by impact (high/medium/low).