git-operations
Skill1 starsChanged 2 months agoApache-2.0View on GitHub
1. When the user asks to commit and/or push changes, use the 'git_commit_and_push' tool directly. Do NOT run 'git add', 'git commit', 'git push' one by one via 'execute_shell_command' - they will not chain with && and wastes tool calls. 2. Only use 'execute_shell_command' with 'git status' or 'git diff' first if you genuinely need to inspect changes before deciding on a commit message. Don't call these more than once per task unless something actually changed. 3. 'git_commit_and_push' always requires…
- Reads credentials
- Commits and pushes
5 other projects use a version of this.
Adopted by
Most recently taken up by
- komluk/scaffoldingtheir own version, first seen Nov 7, 2026
- GoogleCloudPlatform/sciontheir own version, first seen Oct 13, 2026
- m16khb-org/issueopstheir own version, first seen Sep 24, 2026
- poorvith-mp/skills-developertheir own version, first seen Aug 19, 2026
- arnabdeypolimi/claude_code_setuptheir own version, first seen May 5, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- GoogleCloudPlatform/scion★ 2.1ksame name
- komluk/scaffolding★ 16same name
- m16khb-org/issueops★ 6same name
- arnabdeypolimi/claude_code_setup★ 4same name
- poorvith-mp/skills-developer★ 0same name
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 repository4 other files it gives its agents.
- code-navigationSkill
- file-editingSkill
- security-reviewSkill
- unit-testingSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
3
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
- Distinctive: line 6
When the user asks to commit and/or push changes, use the 'git_commit_and_push' tool directly.
- Distinctive: line 10
Only use 'execute_shell_command' with 'git status' or 'git diff' first if you genuinely need to inspect changes before deciding on a commit …
- Distinctive: line 23
Do not chain shell commands with &&, ;, or | - execute_shell_command runs one command at a time by design (this prevents a class of parsing …
“Common” is measured: kept by at least 6 in 10 of the 4 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
Git Operations Skill
Description: Use this whenever the user asks to commit, push, check git status, or do any git-related task in this project.
Rules for this task
- When the user asks to commit and/or push changes, use the 'git_commit_and_push' tool directly. Do NOT run 'git add', 'git commit', 'git push' one by one via 'execute_shell_command' - they will not chain with && and wastes tool calls.
- Only use 'execute_shell_command' with 'git status' or 'git diff' first if you genuinely need to inspect changes before deciding on a commit message. Don't call these more than once per task unless something actually changed.
- 'git_commit_and_push' always requires human confirmation before it actually runs (it returns CONFIRMATION_REQUIRED first). This is intentional - never try to bypass it or assume the user already agreed.
- 'git add -A' inside 'git_commit_and_push' stages ALL changed files, including anything not in .gitignore. If you're unsure whether sensitive files (like .env, credentials, or large data dumps) might get swept in, run 'git status' first and flag it to the user before proceeding.
- Do not chain shell commands with &&, ;, or | - execute_shell_command runs one command at a time by design (this prevents a class of parsing bugs). Call the tool once per command instead.
- This project's remote default branch may not match the local branch name exactly (local: main, remote: master in some setups). If a push fails with an "upstream branch does not match" error, surface the exact git error to the user rather than guessing at a fix - branch/remote mismatches should be resolved by the user, not auto-corrected.
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.