agentleFS
Sign inStart free
gologo13gologo13/agent-skills/skills/git-push/SKILL.md

git-push

Skill0 starsChanged 9 months agoMITView on GitHub

Push current branch to origin and sync with remote updates; keywords: git, rebase. Use only on explicit request; before execution, review diffs and list impact scope.

  • Deletes or force-pushes
  • Commits and pushes

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 1

    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
  1. Very specific:

    Prefer rebase over merge for a linear history.

    line 24
  2. Distinctive:

    If you need to force push after a rebase: you need to ask the user if they want to force push: git push --force-with-lease.

    line 25

“Common” is measured: kept by at least 6 in 10 of the 10 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

Git Push (sync with origin)

Overview

Push current branch to origin and sync with remote updates.

Steps

  1. Fetch and rebase onto latest main (optional but recommended)
    • git fetch origin
    • git rebase origin/main || git rebase --abort (if not on main, rebase your feature branch onto latest main)
  2. Push current branch
    • git push -u origin HEAD
  3. If push rejected due to remote updates
    • Rebase and push: git pull --rebase && git push

Notes

  • Prefer rebase over merge for a linear history.
  • If you need to force push after a rebase: you need to ask the user if they want to force push: git push --force-with-lease.

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