push
Skill2 starsChanged 5 days agoMITView on GitHub
Commit all changes and push to remote.
- Commits and pushes
50 other projects use a version of this.
Adopted by
Most recently taken up by
- snuffish/dotfilestheir own version, first seen Nov 16, 2026
- markmhendrickson/neotomatheir own version, first seen Nov 15, 2026
- toy-crane/claude-code-playbook-templatetheir own version, first seen Nov 10, 2026
- HawkingHuang/claude-skillstheir own version, first seen Nov 8, 2026
- tyrantpiper/travel-pwatheir own version, first seen Nov 8, 2026
- quochuydev/kittheir own version, first seen Nov 8, 2026
Used with
Projects with it also use get-pr-reviews, push-everything and 10 more.
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.
saffron-healthSkillget-pr-reviews
Get nicely formatted output of the last review comments on a PR. Used internally by other skills.
Also in 3 projects that use this
saffron-healthSkillpush-everything
Stage ALL changes in the repository (not just session changes), commit, and push. Use when you need to commit all pending changes.
Also in 3 projects that use this
NVIDIASkillgenerate-spec
Produce a feature specification covering API changes, backward compatibility, cross-language impact, performance, and a file-level change plan. Use when designing a new feature, planning a significant change, or the user asks to spec something out.
Also in 3 projects that use this
ddehartSkillknowledge-graph
Search, capture, and query the claude-code-plugins knowledge graph. Use when asked to "capture this", "add this to the graph", "what do we know about X", "update the graph", "check the graph for X", or when a decision, pattern, or non-obvious fact surfaces mid-session that's worth recording. Also: "log an observation", "what patterns do we have about skill triggering", "any decisions on the knowledge-commons plugin", "what do we know about the commit-creator agent".
Also in 3 projects that use this
anombyte93Skilldiscover
Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.
Also in 4 projects that use this
MicrosoftSkillmerge
Merge changes from the topic branch to the merge base branch. Use when the user wants to merge their session's work back to the base branch.
Also in 3 projects that use this
- +2 more from saffron-health
Other versions50 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 50
- openai/symphony★ 27ksame name
- kdlbs/kandev★ 1.1ksame name
- cashew-labs/libretto★ 911same name
- saffron-health/libretto★ 911same name
- egregore-labs/egregore★ 293same name
- Mooshieblob1/MooshieUI★ 225same name
- team-mirai-volunteer/mirai-gikai★ 214same name
- sterlingcrispin/claude_slash_commands★ 200same name
- Nucleify/Nucleify★ 171same name
- kv0906/pm-kit★ 138same name
40 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 repository24 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- 1passwordSkill
- brainSkill
- brainstormSkill
- bridgeSkill
- claude-switcherSkill
- clear-cacheSkill
- commitSkill
- cross-artifactSkill
- ctoSkill
- diskSkill
- killSkill
- lookSkill
- parseSkill
- pbarSkill
- planSkill
- pruneSkill
- reportSkill
- researchSkill
- swarmSkill
- vibe-auditSkill
- video-editorSkill
- webSkill
- wikiSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.
0
Common
Most of the 43 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Run git status to see what's uncommitted
- Very specific: line 26
Before staging, run the sidecar script if sqlite_tracking is configured in .claude/kit.json:
- Very specific: line 34
If there are uncommitted changes, stage and commit: git add -A && git commit -m "<message>"
- Very specific: line 40
After pushing to origin, push the named subtree to its deploy repo.
- Very specific: line 62
If the name is not found in subtrees, list available names and ask the user.
- Very specific: line 83
If .claude/kit.json has a rules."push" entry, read it and apply it as an additional instruction for this skill.
“Common” is measured: kept by at least 6 in 10 of the 43 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
Push Changes
Stages all files, commits with an auto-generated message, and pushes to remote.
Modifiers
/push— Default. Stages, commits, and pushes to the monorepo remote (origin)./push sub <name>— Stages, commits, pushes to origin, and pushes the named subtree to its deploy repo.
Input
Optional argument: $ARGUMENTS
Procedure
- Run
git statusto see what's uncommitted Regenerate SQLite sidecars (if configured)
Before staging, run the sidecar script if
sqlite_trackingis configured in.claude/kit.json:bash ~/.claude-kit/scripts/sqlite-sidecar.shThe script is a no-op if no
sqlite_trackingis configured in.claude/kit.json.- If there are uncommitted changes, stage and commit:
git add -A && git commit -m "<message>" - Push to origin:
git push Subtree push (only with
submodifier)After pushing to origin, push the named subtree to its deploy repo. Read the subtree config from
.claude/kit.json:{ "subtrees": { "app": { "prefix": "app", "remote": "app", "branch": "main" } } }Resolve the subtree name from the argument:
PREFIX=$(jq -r ".subtrees.\"$NAME\".prefix" .claude/kit.json) REMOTE=$(jq -r ".subtrees.\"$NAME\".remote" .claude/kit.json) BRANCH=$(jq -r ".subtrees.\"$NAME\".branch // \"main\"" .claude/kit.json)If the name is not found in
subtrees, list available names and ask the user.Then push:
git subtree push --prefix="$PREFIX" "$REMOTE" "$BRANCH"Report success and the remote URL.
Rules
- No permission required — Execute immediately without asking
- Concise messages — Summarize what changed, not every detail
- Never skip hooks (
--no-verify) - Include all files —
git add -A, never be selective - If nothing to commit — Just push existing commits
Project overrides
If .claude/kit.json has a rules."push" entry, read it and apply it as an additional
instruction for this skill. Absent file or key means no overrides — that is the normal case.
jq -r '.rules."push" // empty' .claude/kit.json 2>/dev/nullDoes 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.

