agentleFS
Sign inStart free
aymericbeaumetaymericbeaumet/dotfiles/.agents/skills/push/SKILL.md

push

Skill22 starsChanged 2 months agoMITView on GitHub

Synchronize and push existing commits without staging or committing. Use when the user asks to push or publish the current branch.

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

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 42 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    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:

    Do not stage files or create, amend, squash, or otherwise rewrite commits except for the explicit upstream rebase below.

    line 8
  2. Distinctive:

    If rebase conflicts occur, resolve clear conflicts, stage only the resolutions, and continue the rebase.

    line 30
  3. Distinctive:

    Never force-push or bypass hooks.

    line 35

“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

Push

Do not stage files or create, amend, squash, or otherwise rewrite commits except for the explicit upstream rebase below. Preserve all staged and unstaged worktree changes.

  1. Inspect the current branch, worktree and index status, configured upstream, recent commits, and remotes before changing directories. Record the source branch, HEAD, synchronization upstream, and Git's resolved push remote and destination ref. Use @{push} where resolvable and honor branch.<name>.pushRemote, remote.pushDefault, remote.<name>.push, and push.default. The synchronization upstream can differ from the push destination. Fall back to origin and the source branch name only for an unconfigured first publication. Stop when configuration forbids a default push, leaves the target ambiguous, or would publish additional refs.
  2. Require a bonsai worktree using the bonsai skill's existing-work handoff, unless the repository's AGENTS.md designates direct work on its default branch; then stay in the current checkout and skip the handoff. Preserve the recorded source HEAD and destination; leave pending source changes untouched. A new task branch must use --base <source-head> and must not become a different remote branch merely because of the move.
  3. Fetch the recorded remotes. Compare the intended commits with the synchronization upstream, when one exists, and separately with the push destination. When the synchronization upstream is ahead or histories diverged, require clean source and destination worktrees and indexes, then rebase onto that upstream. Recheck the captured source HEAD before synchronization; stop on concurrent changes. Keep the original source branch consistent with any synchronized HEAD without overwriting pending work. Stop if the resulting push would not be a fast-forward; never change its destination to avoid a rejection.
  4. If rebase conflicts occur, resolve clear conflicts, stage only the resolutions, and continue the rebase. If a resolution is ambiguous or risky, abort the rebase and stop the pipeline.
  5. Push the synchronized HEAD to the recorded remote and full destination ref explicitly. If no upstream existed, configure it for the intended source branch after a successful push. Never infer the destination from a temporary task branch's name or upstream.
  6. Never force-push or bypass hooks.

Report the branch, synchronization performed, and push result.

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