agentleFS
Sign inStart free
MrCipherSmithMrCipherSmith/goodai-base/skills/push/SKILL.md

push

Skill0 starsChanged 5 months agoMITView on GitHub

Use when pushing the current branch to the remote, especially when upstream tracking or safety checks are needed.

  • Commits and pushes

49 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use get-pr-reviews, push-everything and 9 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-healthSkill

    get-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-healthSkill

    push-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

  • NVIDIASkill

    generate-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

  • ddehartSkill

    knowledge-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

  • anombyte93Skill

    discover

    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

  • MicrosoftSkill

    merge

    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

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 42 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Run in parallel where possible:

    line 24
  2. Distinctive:

    If there are uncommitted changes → warn and ask if they want to commit first

    line 30
  3. Distinctive:

    If on main or master → warn and ask for confirmation

    line 31
  4. Very specific:

    If branch has no upstream → use git push -u origin <branch>

    line 32
  5. Very specific:

    NEVER use --force unless the user explicitly says "force push"

    line 37
  6. Distinctive:

    NEVER force push to main/master without double confirmation

    line 50
  7. Distinctive:

    If push is rejected (non-fast-forward), suggest git pull --rebase first

    line 52

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Smart Push

Push current branch to remote with safety checks.

Workflow

Phase 1: Pre-flight

Run in parallel where possible:

  1. git status — check for uncommitted changes
  2. git branch -vv — check current branch and tracking info
  3. git log @{upstream}..HEAD --oneline 2>/dev/null — commits to push

Phase 2: Safety Checks

  • If there are uncommitted changes → warn and ask if they want to commit first
  • If on main or master → warn and ask for confirmation
  • If branch has no upstream → use git push -u origin <branch>

Phase 3: Push

  • Normal case: git push
  • No upstream: git push -u origin $(git branch --show-current)
  • NEVER use --force unless the user explicitly says "force push"

Phase 4: Confirm

Show result: confirm push success with commit count.

Arguments

  • /push — standard push
  • /push --force — force push (only when explicitly requested, warn if main/master)
  • /push origin <branch> — push to specific remote/branch

Rules

  • NEVER force push to main/master without double confirmation
  • NEVER use --no-verify
  • If push is rejected (non-fast-forward), suggest git pull --rebase first

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free