commit-push
Skill0 starsChanged 4 months agoMITView on GitHub
Commit staged (or all) changes and push to the current remote branch. Use when the user says /commit-push, wants to commit and push without opening a PR, says "push this up", "commit and push", or "ship this". Do NOT use when the user wants to open a pull request — that's /commit-push-pr.
- Commits and pushes
19 other projects use a version of this.
Adopted by
Most recently taken up by
- Adonis0123/adonis-skillstheir own version, first seen Nov 7, 2026
- Ssoulisack/claude-skillstheir own version, first seen Oct 15, 2026
- Diego-Romero/claude-skillstheir own version, first seen Oct 13, 2026
- Nucleify/Nucleifytheir own version, first seen Oct 8, 2026
- Eatgrapes/WinIslandtheir own version, first seen Oct 8, 2026
- anyproto/anytype-tstheir own version, first seen Oct 8, 2026
Used with
Projects with it also use open-pr.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Google CloudSkillopen-pr
Commits local changes to a new Git branch and opens a GitHub pull request through the configured GitHub MCP server. Use when proposing code changes in a new pull request. Don't use for local-only commits without a remote GitHub repository.
Also in 3 projects that use this
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- anyproto/anytype-ts★ 9.1ksame name
- Eatgrapes/WinIsland★ 405same name
- Nucleify/Nucleify★ 171same name
- DataCovey/nornweave★ 30same name
- tykisgod/quick-question★ 12same name
- Adonis0123/adonis-skills★ 4same name
- Mitscherlich/skills★ 3same name
- wzh4464/claude-skills★ 3same name
- d-gangz/dgang-skills★ 2same name
- gtapps/skills★ 2same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- design-modeSkill
- md2pdfSkill
- overnight-parkSkill
- overnightSkill
- rename-to-dirSkill
- screenshotSkill
- skillspectorSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 8
Commit the current changes and push to origin.
- Distinctive: line 12
Run git status and git diff --cached to see what's staged.
- Distinctive: line 16
Run git push. If the branch has no upstream, run git push -u origin HEAD.
- Distinctive: line 28
Do not open a PR or suggest one unprompted
- Distinctive: line 29
Do not amend previous commits
- Distinctive: line 30
Do not force push
- Distinctive: line 31
Do not skip the staged-file verification step — missing files before push has been a recurring issue
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Commit and Push
Commit the current changes and push to origin. No PR creation.
Steps
- Run
git statusandgit diff --cachedto see what's staged. If nothing is staged, stage all tracked changes withgit add -u. - Show the user what will be committed and confirm the scope looks right.
- Write the commit message to a session-unique path using the Write tool — never heredocs or
-m, since the Bash tool injects ANSI codes that end up verbatim in the commit. Use the session scratchpad dir if one exists, otherwise/tmp/msg-<repo>-<short-sha-or-timestamp>.txt. Never a shared path like/tmp/msg.txt: concurrent Claude sessions clobber it mid-commit and you commit the other session's message. - Run
git commit -F <that path>. - Run
git push. If the branch has no upstream, rungit push -u origin HEAD. - Report the pushed commit hash and branch.
Commit message format
- One-line summary (imperative mood, ≤72 chars)
- Blank line, then body if needed
- Focus on why, not what — the diff shows the what
- Match the repo's existing commit style (check
git log --oneline -5)
What not to do
- Do not open a PR or suggest one unprompted
- Do not amend previous commits
- Do not force push
- Do not skip the staged-file verification step — missing files before push has been a recurring issue
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.