git-commit-push
Skill109 starsChanged 35 days agoMITView on GitHub
Stage, commit, and push changes to remote repository with approval gate
- Commits and pushes
9 other projects use a version of this.
Adopted by
Most recently taken up by
- limi58/skillstheir own version, first seen Nov 7, 2026
- aktsmm/Agent-Skillstheir own version, first seen Nov 1, 2026
- l3rowniecakez/Claude_Skilltheir own version, first seen Oct 19, 2026
- DailybotHQ/deepworkplan-websitetheir own version, first seen Oct 9, 2026
- farm-fe/farmtheir own version, first seen Oct 8, 2026
- gogf/gftheir own version, first seen Oct 8, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- gogf/gf★ 13ksame name
- farm-fe/farm★ 5.6ksame name
- aktsmm/Agent-Skills★ 26same name
- DailybotHQ/deepworkplan-website★ 15same name
- Mingo07-dev/claude_skills★ 2same name
- ZhaoYis/My-Skills★ 2same name
- andyshen1121/skills★ 1same name
- l3rowniecakez/Claude_Skill★ 0same name
- limi58/skills★ 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 repository61 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adviseSkill
- ai-crystallizeSkill
- analyze-kbSkill
- auto-discoverySkill
- benchmark-memorySkill
- brain-mergeSkill
- changelog-protocolSkill
- coherence-sweepSkill
- compute-lifecycleSkill
- create-articleSkill
- create-explanatory-imageSkill
- decideSkill
- deep-researchSkill
- detect-tensionsSkill
- dialecticSkill
- domain-watchSkill
- elicitation-techniquesSkill
- epistemic-classificationSkill
- epub-chapter-extractorSkill
- extract-document-insightsSkill
- extract-insightsSkill
- find-connectionsSkill
- first-runSkill
- get-perspective-onSkill
- get-youtube-transcriptSkill
- graduate-insightsSkill
- incubation-loopSkill
- ingest-sourceSkill
- insight-capture-formatSkill
- insight-interviewSkill
- integrate-recent-notesSkill
- learn-new-thingsSkill
- manage-reference-dataSkill
- manage-thinking-topicsSkill
- manage-watching-domainsSkill
- multi-format-book-extractorSkill
- nano-banana-image-generatorSkill
- propagate-changeSkill
- quick-searchSkill
- reasoning-checksSkill
- recallSkill
- ref-auditSkill
- ref-bridgeSkill
- ref-ingestSkill
- ref-querySkill
- ref-reconcileSkill
- ref-refreshSkill
- refresh-indexSkill
- ref-supersedeSkill
- scheduled-runSkill
- scope-mountSkill
- search-vaultSkill
- self-diagnosticSkill
- start-hereSkill
- synthesize-insightsSkill
- talkSkill
- test-memory-systemSkill
- think-about-itSkill
- update-changelogSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Commit and push changes to the remote repository.
- Distinctive: line 43
If no changes, inform user and exit.
- Distinctive: line 62
Ask for commit message (suggest based on changes)
- Distinctive: line 65
Use AskUserQuestion with options:
- Distinctive: line 89
Ask which files to stage
- Distinctive: line 147
Always shows diff before committing (safety gate)
- Very specific: line 149
Does NOT use --force push (safety)
- Distinctive: line 150
Does NOT amend existing commits (safety)
“Common” is measured: kept by at least 6 in 10 of the 6 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 Commit and Push
Commit and push changes to the remote repository. Shows diff for approval before committing.
Purpose
Safely commit and push all staged and unstaged changes to the remote repository. Presents changes for review before committing to prevent accidental commits.
State Dependencies
| Source | Location | Read | Write | Description |
| Git status | .git/ | X | Current repo state | |
| Working directory | ./ | X | Modified files | |
| Remote repository | origin | X | Push destination |
Prerequisites
- Git repository initialized
- Remote origin configured
- Changes to commit (untracked or modified files)
Process
Step 1: Check Repository State
# Show current branch
git branch --show-current
# Check if there are changes to commit
git status --shortIf no changes, inform user and exit.
Step 2: Review Changes (APPROVAL GATE)
Present the changes for review:
# Show summary of changes
git status
# Show detailed diff of modified files (not untracked)
git diff
# Show staged changes if any
git diff --cachedAsk user:
- Show the list of files that will be committed
- Ask for commit message (suggest based on changes)
- Confirm before proceeding
Use AskUserQuestion with options:
- "Commit all changes" (Recommended)
- "Select specific files"
- "Cancel"
Step 3: Stage and Commit
Based on user choice:
If "Commit all changes":
# Stage all changes
git add -A
# Commit with user-provided message
git commit -m "$(cat <<'EOF'
[commit message here]
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
EOF
)"If "Select specific files":
- Ask which files to stage
- Stage only those files
- Commit
Step 4: Push to Remote
# Push to current branch's upstream
git push
# If no upstream, push with -u flag
git push -u origin $(git branch --show-current)Step 5: Verify
# Confirm push succeeded
git log --oneline -1
# Show remote status
git statusCompletion Checklist
- Repository state checked
- Changes reviewed by user
- Commit message approved
- Changes committed
- Pushed to remote
- Push verified
Error Recovery
| Error | Recovery |
| No changes to commit | Inform user, exit gracefully |
| No remote configured | Ask user to configure: git remote add origin <url> |
| Push rejected (non-fast-forward) | Suggest git pull --rebase first |
| Authentication failed | Check SSH keys or credentials |
| Branch protection | Inform user, suggest PR workflow |
Usage Examples
Basic usage:
/git-commit-pushAfter a work session:
User: commit and push my changes
Agent: [runs this skill]Notes
- Always shows diff before committing (safety gate)
- Adds Co-Authored-By trailer for AI contributions
- Does NOT use
--forcepush (safety) - Does NOT amend existing commits (safety)
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.

