Create a GitHub pull request with the project's PR template fully populated. Analyzes the branch diff, fills in "What changed", "Issue", "How to test", "A11y impact", "Definition of Done", and other sections. Use this skill whenever the user wants to create a PR, open a pull request, submit their branch for review, or says things like "make a PR", "open a PR", "submit this for review", or "I'm ready to create a pull request" — even if they don't use the exact phrase "pull request".
88
88%
Does it follow best practices?
Impact
84%
1.35xAverage score across 3 eval scenarios
Passed
No known issues
Backend PR with ticket extraction and A11y handling
Ticket number extracted
100%
100%
GitHub issue link format
0%
100%
A11y backend-only box checked
100%
100%
Automated tests DoD checked
100%
100%
Form validations DoD unchecked
0%
100%
Screenshots N/A for backend
100%
100%
What changed has file breakdown
100%
100%
How to test includes test commands
100%
100%
PR title under 70 chars
0%
0%
Conventional commit title style
0%
0%
Links section present
100%
100%
Frontend PR with A11y unchecked and screenshots placeholder
A11y checkboxes unchecked
0%
0%
Screenshots placeholder not N/A
100%
100%
Ticket number extracted
100%
100%
GitHub issue link format
0%
100%
What changed has file/area breakdown
60%
100%
How to test includes UI steps
100%
100%
How to test includes test command
100%
100%
Automated tests DoD checked
100%
100%
PR title under 70 chars
0%
0%
Conventional commit title style
0%
0%
Refactoring PR with HEREDOC script and Links from commits
Refactoring DoD checked
100%
100%
Links section references PR #987
100%
100%
A11y backend-only checked
100%
100%
Screenshots N/A
100%
100%
Ticket number extracted
100%
100%
GitHub issue link format
0%
100%
create-pr.sh uses HEREDOC
0%
100%
create-pr.sh has gh pr create
100%
100%
Automated tests DoD checked
100%
100%
PR title under 70 chars
0%
100%
Conventional commit title
0%
100%
e2a9461
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.