commit_push
Skill21 starsChanged 3 months agoMITView on GitHub
Format code, review changes, commit, and push to remote
- Commits and pushes
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- MarcusJellinghaus/mcp-workspaceedited, first seen Nov 14, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- MarcusJellinghaus/mcp-workspace★ 4944% 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 repository21 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
- rebaseSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Follow this process to commit and push your changes:
- Very specific: line 20
Use mcp__mcp-tools-py__run_format_code to format all code (black + isort).
- Very specific: line 23
Use mcp__mcp-workspace__git with command "status" to check working directory state.
- Very specific: line 24
Use mcp__mcp-workspace__git with command "diff" to review the changes.
- Distinctive: line 30
Create a commit with a clear, conventional commit message:
- Distinctive: line 33
Keep summary under 50 characters
- Distinctive: line 41
If the branch doesn't exist on remote yet:
≈ “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 (black + isort).
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. Stage Changes
Stage all relevant changes (exclude any files that shouldn't be committed).
4. Commit
Create a commit with 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
5. Push
git pushIf the branch doesn't exist on remote yet:
git push -u origin HEADDoes 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.

