Install any skill in seconds. Free to start, no credit card required.
Get Started Free →joshukraine/create-pr
Create a pull request with auto-generated description, issue linking, ROADMAP updates, and PR-metadata validation.
Passed 12 of 19 test cases with the skill, and 11 of 19 without it.
and 1 more in the full report
3 fixed11 passed either way7 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
While checking candidates for issue #300, a comment states 'this PR resolves #305'. How should issue #305 be prefixed in the PR description?
| Checked | Without skill | With skill |
|---|---|---|
| Uses the Closes prefix for candidate issue 305 | Missed | Passed |
The instructions your model reads when the skill loads.
Create a pull request from the current branch with proper formatting and issue linking.
All flags are optional. By default, the issue number is inferred from the branch name and the PR is created as ready-to-review.
--issue N: Override automatic issue linking with a specific issue number (or comma-separated list: --issue 123,175)--skip-issue-link: Skip issue linking entirely--draft: Create PR as draftVerify prerequisites:
main/masterGenerate PR title:
Analyze commits for description:
git log origin/<base-branch>..HEAD --oneline (use the base branch identified in step 1)Create comprehensive description:
Update ROADMAP:
docs/prd/ROADMAP.md[x]) and commit the change to the branch before creating the PRtest cases passed, vs 11 / 19 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.