Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →saffron-health/push
Commit and push changes, creating or updating a PR as needed.
Passed 9 of 16 test cases with the skill, and 11 of 16 without it.
2 fixed10 passed either way5 still failing5 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
A unit test failed on CI after pushing my PR. Should I automatically fix the failing test locally, commit it, and push it immediately back to GitHub?
| Checked | Without skill | With skill |
|---|---|---|
| Requires explicit user review and approval before committing and pushing fixes. | 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:
Commit the changes. 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.
When writing or updating a PR title and description, always base them on the full diff against main (git diff main...HEAD), not just the most recent commits. The title and description should accurately summarize the entire set of changes in the PR.
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 11 / 16 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.