Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
94
92%
Does it follow best practices?
Impact
95%
1.69xAverage score across 3 eval scenarios
Passed
No findings from the security scan
pr-title-format, draft-pr-creation, pr-description-content
PR title uses [codex] prefix
0%
100%
Creates draft PR with correct flags
0%
100%
PR description covers issue and user impact
100%
100%
PR description covers root cause
100%
100%
PR description covers the fix
100%
100%
PR description covers validation
100%
100%
branch-naming-from-main, commit-naming
Creates branch with codex/ prefix
0%
100%
Uses terse commit message
100%
100%
Checks branch before creating new one
0%
100%
pre-push-checks, push-with-tracking
Runs checks before git push
100%
100%
Uses -u flag when pushing
100%
100%
Handles check failures appropriately
40%
40%
f627ab5
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.