Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lifinance/create-pr
Create a pull request for the current branch: creates a new branch if needed, commits staged/unstaged changes, pushes, and opens a PR using the repo's pull_request_template.md.
Passed 4 of 11 test cases with the skill, and 4 of 11 without it.
and 2 more in the full report
4 fixed3 passed either way10 still failing5 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am opening a small doc tweak PR. I explicitly opt out of creating or linking any Linear ticket for this PR (option 's'). How should the Linear section in the PR template be rendered?
| Checked | Without skill | With skill |
|---|---|---|
| Places <!-- No Linear task --> in the Linear section of the PR template | Missed | Passed |
The instructions your model reads when the skill loads.
User says any of:
/create-pr [branch-name]feat/short-description).--draft in step 11. All other steps (template, Linear ticket, tests) apply unchanged.s at the step 5 prompt) — the absence of a known ticket is never an opt-out.This skill creates PRs. For editing an existing PR's title/body, follow CLAUDE.md →
"Creating and editing PRs via gh" (uses gh api -X PATCH with a JSON payload).
There is no local CodeRabbit pre-flight anymore (/pr-ready was removed — the CLI was
hitting rate limits and wasting review cycles). Cloud CodeRabbit still runs in GitHub CI
on every PR as the review backstop.
Run git status and git diff HEAD to understand:
gh pr view)Handle these edge cases before continuing:
test cases passed, vs 4 / 11 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.