commit_push
Skill49 starsChanged 2 days agoMITView on GitHub
Format code, review changes, commit, and push to remote
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- MarcusJellinghaus/mcp-tools-pyedited, first seen Aug 31, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- MarcusJellinghaus/mcp-tools-py★ 2167% same
Wrote their own version · 0
None found.
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 repository22 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- check_branch_statusSkill
- discussSkill
- implementation_approveSkill
- implementation_finaliseSkill
- implementation_needs_reworkSkill
- implementation_new_tasksSkill
- implementation_reviewSkill
- implementation_review_supervisorSkill
- implement-directSkill
- issue_analyseSkill
- issue_analyse_supervisorSkill
- issue_approveSkill
- issue_createSkill
- issue_requirementsSkill
- issue_updateSkill
- plan_approveSkill
- plan_reviewSkill
- plan_review_supervisorSkill
- plan_updateSkill
- pr_comment_triageSkill
- rebaseSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 5 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Follow this process to commit and push your changes:
- Very specific: line 19
Use mcp__mcp-tools-py__run_format_code to format all code with the project's configured formatter.
- Very specific: line 22
Use mcp__mcp-workspace__git with command "status" to check working directory state.
- Very specific: line 23
Use mcp__mcp-workspace__git with command "diff" to review the changes.
- Very specific: line 26
Call mcp__mcp-workspace__git_commit with message and paths built from git status:
- Distinctive: line 30
If no paths remain, skip the commit and go to step 4.
- Distinctive: line 32
Use a clear, conventional commit message:
- Distinctive: line 35
Keep summary under 50 characters
- Very specific: line 38
If the result starts with Nothing to commit, go to step 4 (earlier commits may be unpushed).
- Very specific: line 39
If it starts with Error:, report it and stop — do not push.
- Very specific: line 42
Call mcp__mcp-workspace__git_push (no arguments).
- Distinctive: line 44
If it refuses (e.g. on the default branch), report it and stop.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Commit and Push Changes
Follow this process to commit and push your changes:
1. Format Code
Use mcp__mcp-tools-py__run_format_code to format all code with the project's configured formatter.
2. Review Changes
Use mcp__mcp-workspace__git with command "status" to check working directory state.
Use mcp__mcp-workspace__git with command "diff" to review the changes.
3. Commit
Call mcp__mcp-workspace__git_commit with message and paths built from git status:
- Include modified, new and deleted files, and both the old and the new path of a rename
(
git_commitcommits only the given paths). - Exclude any files that shouldn't be committed.
- If no paths remain, skip the commit and go to step 4.
Use a clear, conventional commit message:
- Use format:
type(scope): description - Types: feat, fix, docs, style, refactor, test, chore
- Keep summary under 50 characters
- No Claude Code footer or attribution in commit message
If the result starts with Nothing to commit, go to step 4 (earlier commits may be unpushed).
If it starts with Error:, report it and stop — do not push.
4. Push
Call mcp__mcp-workspace__git_push (no arguments).
If it refuses (e.g. on the default branch), report it and stop. If step 3 made a commit, state that the commit exists locally and is unpushed.
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.

