push
Skill13 starsChanged 7 months agoMITView on GitHub
Push the current branch to the configured remote. Use when the user explicitly asks to push changes.
- Commits and pushes
49 other projects use a version of this.
Adopted by
Most recently taken up by
- 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
- laz3rjenkins/atomic-commitstheir own version, first seen Nov 8, 2026
- AsiaOstrich/EngramGraphtheir own version, first seen Nov 8, 2026
- toy-crane/claude-code-playbook-templatetheir 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 versions49 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 49
- openai/symphony★ 27ksame name
- kdlbs/kandev★ 1.1ksame name
- cashew-labs/libretto★ 898same name
- saffron-health/libretto★ 883same name
- egregore-labs/egregore★ 293same name
- Mooshieblob1/MooshieUI★ 222same name
- team-mirai-volunteer/mirai-gikai★ 214same name
- sterlingcrispin/claude_slash_commands★ 200same name
- Nucleify/Nucleify★ 171same name
- kv0906/pm-kit★ 138same name
39 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 repository19 other files it gives its agents.
- agent-auditSkill
- codebase-auditSkill
- commitSkill
- design-and-specSkill
- dispatching-parallel-agentsSkill
- doc-driftSkill
- execution-planningSkill
- explain-codeSkill
- post-implementationSkill
- python-auditSkill
- receiving-code-reviewSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- terraform-auditSkill
- test-driven-developmentSkill
- trace-codeSkill
- typescript-auditSkill
- verification-before-completionSkill
- writing-plansSkill
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 42 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 17
If there are no configured remotes, stop here and say so.
- Distinctive: line 19
If already up to date (zero unpushed commits AND upstream exists), report "already up to date" and stop — do not push unnecessarily.
- Distinctive: line 21
If the working tree is dirty (uncommitted changes exist), warn the user but do not block.
- Distinctive: line 25
If the branch is main or master:
- Distinctive: line 28
Do not push, do not continue.
- Very specific: line 30
Only allow pushes on branches matching feature/*.
- Distinctive: line 34
Read the project steering files for any remote or branch push constraints.
- Distinctive: line 54
If a constraint from Step 2 blocks the push, stop and explain why
“Common” is measured: kept by at least 6 in 10 of the 42 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 the current branch to the remote. Work through each step in order and stop immediately if a hard stop condition is met.
Step 1 — Understand current state
Run in parallel:
git branch --show-current— current branch namegit status --short— check for uncommitted changesgit remote -v— list configured remotes
Then run: git log @{u}..HEAD --oneline 2>/dev/null — show unpushed commits. If this fails (no upstream set), note that this is the first push for this branch.
If there are no configured remotes, stop here and say so.
If already up to date (zero unpushed commits AND upstream exists), report "already up to date" and stop — do not push unnecessarily.
If the working tree is dirty (uncommitted changes exist), warn the user but do not block.
Step 1.5 — Branch safety check
If the branch is main or master:
- STOP immediately. Do not ask. Do not proceed.
- Say exactly: "BLOCKED: You are on
<branch>. Pushing to main/master is not allowed. Switch to afeature/*branch first." - Do not push, do not continue.
Only allow pushes on branches matching feature/*.
Step 2 — Check push constraints
Read the project steering files for any remote or branch push constraints. Look for:
- Protected remotes on specific branches
- Branches that should never be pushed directly
Note any constraints — apply them in Step 3.
Step 3 — Push
Push the current branch to origin:
# First push (no upstream set):
git push -u origin <branch>
# Subsequent pushes (upstream already set):
git push origin <branch>Rules:
- Never use
--forceor-funless the user explicitly requested it in their message - If a constraint from Step 2 blocks the push, stop and explain why
Step 4 — Report results
Show a clear summary:
Push Results:
- Branch: <branch>
- origin (<url>): ✓ pushed / ✗ failed: <error>
- Commits pushed: <n>Then remind: "Create a merge request on GitLab if one doesn't exist yet."
Hard stops
- No remotes configured — stop immediately.
- On main/master — stop immediately, do not push.
- Force push — never add
--forceor-fwithout explicit user instruction.
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.

