PR helper skills: review and resolve PR comments, and draft structured PR descriptions.
97
92%
Does it follow best practices?
Impact
98%
1.44xAverage score across 10 eval scenarios
Advisory
Suggest reviewing before use
Review comments endpoint
100%
100%
Authenticated user lookup
100%
100%
Exclude self-replied
100%
100%
Top-level only filtering
100%
100%
Agent commit timestamp
50%
70%
Since parameter usage
100%
100%
First-run handling
100%
100%
Stop when empty
30%
70%
Reply-user matching
100%
100%
Test coverage
100%
100%
Used pr-comment-resolver skill
80%
100%
Three decision categories
100%
100%
Generated file recognition
100%
100%
OpenAPI generated file
70%
100%
Defer large refactor
100%
100%
Rationale provided
100%
100%
Defer/disagree reasoning
100%
100%
User confirmation plan
100%
100%
Plan shows all comments
100%
100%
Critical assessment
100%
100%
Source file targets only
100%
100%
Used pr-comment-resolver skill
30%
80%
Source schema edited
100%
100%
Generated types not hand-edited
100%
100%
Generation script executed
100%
100%
Lint verification
100%
100%
Minimal source changes
100%
100%
Handler updated consistently
100%
100%
Staged files listed
100%
100%
Commit message format
100%
100%
Co-authored-by line
0%
100%
Workflow ordering
100%
100%
Used pr-comment-resolver skill
0%
70%
Replies endpoint
100%
100%
Top-level comment ID
100%
100%
Diagnose before fallback
100%
100%
Verify IDs on failure
100%
100%
Issue comment fallback last
30%
100%
Short addressed reply
100%
100%
Short defer reply
60%
100%
Disagree with reason
100%
100%
Commit message format
80%
100%
Co-authored-by attribution
0%
100%
Used pr-comment-resolver skill
20%
70%
Review comments API
100%
100%
Comment filtering stage
37%
100%
Assessment stage
70%
100%
User confirmation stage
100%
100%
Source-only editing
0%
80%
Regeneration stage
0%
100%
Verification stage
0%
100%
Correct workflow order
60%
100%
Reply via thread endpoint
37%
100%
One commit per comment
0%
75%
Commit format
37%
100%
Empty result handling
50%
100%
Used pr-comment-resolver skill
40%
100%
Summary heading
0%
100%
Context heading
100%
100%
Why heading
0%
100%
What changed heading
70%
100%
Links heading
0%
100%
ENG-4421 referenced
100%
100%
Grouped change bullets
100%
100%
Not a raw diff paste
100%
100%
How to test heading
70%
100%
Plain-language summary
0%
100%
Used pr-description skill
20%
100%
Security or rollout called out
100%
100%
SEC-215 in links area
100%
100%
Summary heading
100%
100%
Context heading
0%
100%
Why heading
0%
100%
What changed heading
0%
100%
Links heading
75%
100%
How to test has steps
100%
100%
What changed has bullets
100%
100%
No placeholder-only body
100%
100%
Used pr-description skill
50%
100%
BILL-901 referenced
100%
100%
Related PR called out
100%
100%
Design or doc link
100%
100%
Summary heading
100%
100%
Context heading
0%
100%
Why heading
0%
100%
What changed heading
0%
100%
Links heading
37%
100%
What changed bullets
100%
100%
Not file-list-only
100%
100%
Used pr-description skill
40%
100%
Large scope acknowledged
100%
100%
PLAT-550 referenced
100%
100%
Area-labeled bullets
100%
100%
Summary heading
0%
100%
Context heading
0%
100%
Why heading
0%
100%
What changed heading
50%
100%
Links heading
25%
100%
Context not diff replay
77%
100%
How to test or review path
100%
100%
Used pr-description skill
30%
100%
No ticket stated
100%
100%
Summary heading
100%
100%
Context heading
0%
100%
Why heading
0%
100%
What changed heading
0%
100%
Links heading
22%
100%
How to test heading
100%
100%
What changed bullets
100%
100%
No fake ticket ID
100%
100%
Plain language
100%
100%
Used pr-description skill
30%
100%
Table of Contents