Generate structured PR descriptions from diffs, add review checklists, risk assessments, and test coverage summaries. Use when the user says "write a PR description", "improve this PR", "summarize my changes", "PR review", "pull request", or asks to document a diff for reviewers.
95
93%
Does it follow best practices?
Impact
100%
2.04xAverage score across 3 eval scenarios
Passed
No known issues
PR description template structure
Summary section
100%
100%
Changes markdown table
0%
100%
Category column
0%
100%
Files column with backticks
0%
100%
Key change column
0%
100%
Why section
40%
100%
Testing npm test
10%
100%
Testing smoke test
30%
100%
Testing coverage
0%
100%
Risks & Rollback section
100%
100%
Breaking? field
0%
100%
Rollback instructions
0%
100%
Risk level (low/medium/high)
0%
100%
Conditional review checklist by file category
Source checklist section
100%
100%
Debug statements check
0%
100%
Function length check
0%
100%
Error handling check
100%
100%
Test checklist section
100%
100%
AAA pattern item
0%
100%
No flaky tests item
50%
100%
Config checklist section
100%
100%
No hardcoded secrets check
100%
100%
Env vars documented check
50%
100%
Security section present
100%
100%
Security checklist item
100%
100%
Large PR detection and split recommendation
Large PR warning
100%
100%
Split suggestion
100%
100%
cherry-pick command
0%
100%
New branch command
0%
100%
Feature area grouping
100%
100%
Multiple split groups named
100%
100%
Risk level stated
70%
100%
Breaking changes addressed
80%
100%
93c57b2
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.