Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fcakyon/create-pr
This skill should be used when user asks to "create a PR", "make a pull request", "open PR for this branch", "submit changes as PR", "push and create PR", or explicitly invokes "create-pr".
Passed 17 of 18 test cases with the skill, and 8 of 18 without it.
and 9 more in the full report
10 fixed7 passed either way0 still failing1 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
After publishing a pull request using `gh pr create`, what specific GitHub CLI command should be run to inspect and verify the published title, body text, and render integrity?
| Checked | Without skill | With skill |
|---|---|---|
| Executes `gh pr view <pr> --json title,body,url` after publishing. | Missed | Passed |
The instructions your model reads when the skill loads.
Create a PR a reviewer can understand without reading the conversation. Use extra invocation text and session findings to explain the problem, final behavior, and evidence. Follow the user's requested format and the target repo's guidance.
Inspect the scope and base
git status, staged changes, and the current branch.git merge --ff-only <remote>/<base>.
Preserve dirty work and stop if fast-forwarding fails. Do not reset it away.Finish and inspect the change
/simplify on the staged diff before committing and apply its findings. Docs-only
diffs are a no-op. Follow commit-staged for any staged changes.git diff <remote>/<base>...HEAD across all commits. For an existing PR, use its
actual base and head, or gh pr diff <pr> if this checkout is on another branch.Write and publish
update-pr-summary
rather than opening a duplicate.--body-file to gh.
Never interpolate text into a shell command or include command output by accident.--title, --body-file, and -a @me.gh pr list --repo <owner>/<repo> --author @me --limit 5 --json reviewRequests.gh pr view <pr> --json title,body,url.
Check code fences, tables, links, and preserved media. For visual changes, open the PR
and verify the images render. Report the URL and any incomplete verification.test cases passed, vs 8 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.