Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →brycewang-stanford/commit-push-pr
Commit changes, push to remote, and create a pull request.
Passed 11 of 17 test cases with the skill, and 12 of 17 without it.
1 fixed13 passed either way6 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
I made edits across several files. Before asking for my commit message, what commands should be run to inspect current branch, concise status, recent commits, and stat diff?
| Checked | Without skill | With skill |
|---|---|---|
| Gathers current branch using git branch --show-current | Passed | Passed |
| Gathers short status using git status --short | Missed | Passed |
| Gathers log history using git log --oneline -5 | Missed | Passed |
| Gathers diff statistics using git diff --stat | Missed | Passed |
The instructions your model reads when the skill loads.
Automate the git workflow for completing a feature or fix.
Before proceeding, gather this information:
!git branch --show-current!git status --short!git log --oneline -5!git diff --statReview Changes
git status for all modified/added filesRun Pre-commit Checks
ruff format . (if Python files changed)ruff check . (if Python files changed)pytest (if tests exist)Stage and Commit
git add <files>feat: for new featuresfix: for bug fixesdocs: for documentationrefactor: for refactoringtest: for testschore: for maintenancePush to Remote
git push -u origin HEADCreate Pull Request
test cases passed, vs 12 / 17 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.