Create and submit a GitHub PR from the current branch
64
45%
Does it follow best practices?
Impact
96%
1.92xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/pr-submit/SKILL.mdFull PR workflow steps
git status step
100%
100%
git diff step
100%
100%
git log step
100%
100%
Branch prefix decision
30%
100%
New branch creation
100%
100%
Multiple commits for unrelated changes
0%
100%
Push with -u flag
100%
100%
gh pr create usage
100%
100%
Changelog generation step
0%
100%
Changelog commit and push
10%
100%
PR description update step
0%
100%
PR URL returned
33%
100%
Uncommitted changes handling
git status inspection
100%
100%
git diff inspection
100%
100%
git log inspection
50%
100%
Branch prefix consideration
85%
100%
New branch creation
100%
100%
Identifies unrelated changes
100%
100%
Separate commits for separate concerns
100%
100%
Push with -u flag
0%
100%
gh pr create usage
100%
100%
Post-PR steps mentioned
0%
0%
Post-PR completion steps
git status in log
100%
100%
git diff in log
100%
100%
git log in log
40%
100%
Branch prefix addressed
37%
100%
Push with -u flag
100%
100%
gh pr create used
100%
100%
Changelog command with PR number
0%
100%
Changelog files committed
0%
100%
Changelog files pushed
0%
100%
PR description update command
0%
100%
PR URL recorded
100%
100%
Post-PR steps ordered correctly
0%
100%
ea296ba
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.