Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →saffron-health/push-everything
Stage ALL changes in the repository (not just session changes), commit, and push.
Passed 17 of 20 test cases with the skill, and 9 of 20 without it.
and 7 more in the full report
10 fixed10 passed either way3 still failing1 broke
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.
I am submitting a PR that adds a new user search endpoint to the REST API. Which category label should be attached to the PR for release notes?
| Checked | Without skill | With skill |
|---|---|---|
| The output selects the enhancement label. | Missed | Passed |
The instructions your model reads when the skill loads.
If on main, checkout a new branch first.
If on a non-main branch where the existing PR is already merged, the uncommitted changes are likely unrelated to that branch. In this case:
Stage and commit ALL the changes in the git repo (not just the ones in this session). Use gh cli to check if a PR exists for this branch. If no PR exists, create one with an appropriate title and description. If a PR exists, query its current title and description and update them if the new changes warrant it. Push the changes.
Ignore developer tooling changes (e.g. changes to .gitignore, or agent skills, or anything in dev-tools or .bin) in the commit message or PR title/description, unless the PR is solely about those changes.
When creating or updating a PR in this repo, make sure it has a changelog label so GitHub Releases can categorize it correctly.
Prefer one of:
enhancementbugdocumentationIf the correct label is unclear, prefer enhancement.
If the PR should be excluded from release notes, use skip-changelog.
Use skip-changelog for PRs focused only on developer tooling changes, such as agent skills, workflow plumbing, local tooling, or similar maintenance that should not appear in user-facing release notes.
When the PR body contains Markdown code spans/backticks, parentheses, angle brackets, or shell-sensitive characters, do not pass it directly via --body "..." because shells can mangle it.
Use --body-file with stdin/heredoc instead:
cat <<'EOF' | gh pr create --base main --head <branch> --title "<title>" --body-file -
test cases passed, vs 9 / 20 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.