agentleFS
Sign inStart free
princessingprincessing/claude-skills/skills/commitpush/SKILL.md

commitpush

Skill1 starsChanged 4 months agoMITView on GitHub

Commit the relevant changes with a focused, well-written message and push to the current branch. Use when the user says "commitpush", "commit and push", "/commitpush", "ship this", or otherwise asks to stage, commit, and push work in one step.

  • Commits and pushes

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. thatjuan/agent-skills★ 1same name
    2. laz3rjenkins/atomic-commits★ 0same name

    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 repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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
  1. Distinctive:

    Survey: Run git branch --show-current and git status --short.

    line 30
  2. Distinctive:

    Message: Write a concise, imperative subject (≤ ~72 chars) describing what changed and why.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Commit and Push

Stage the relevant change(s), commit with a clear message, and push to the current branch — in one step. This skill exists so "commit and push" is one consistent, disciplined action instead of re-deriving the staging/message/push dance each time.

Invoking this skill is the explicit authorization to commit AND push (it overrides any standing "don't commit/push unless asked" rule for this run only).

Hard rules

  • Focused commits only. Stage only the files/hunks relevant to the work being shipped. NEVER git add -A / git add . when the worktree has unrelated dirty or untracked files. If the user named a target (a file, a feature, "the skill"), stage exactly that. If they didn't, infer the smallest coherent set and state which files you staged so they can catch a wrong guess.
  • Never the default branch (unless that's genuinely the workflow). If git branch --show-current is main/master, pause and confirm before committing there — most projects want a feature branch. (If the user's flow is trunk-based and they've said so, proceed.)
  • No unrelated edits. This skill only stages, commits, and pushes what's already in the worktree. It does not edit code.

Steps

  1. Survey. Run git branch --show-current and git status --short. Confirm before committing to main/master.
  2. Select. Determine the focused set of paths to stage (see Hard rules). When in doubt about scope, ask rather than over-stage.
  3. Stage. git add <those paths> (explicit paths, never -A). Confirm with git status --short
    • git diff --cached --stat that ONLY the intended paths are staged.
  4. Message. Write a concise, imperative subject (≤ ~72 chars) describing what changed and why. Match the repo's existing commit style (skim git log --oneline). No "Generated by" / tooling footers unless the user asks.
  5. Commit. git commit -m "<message>".
  6. Push. git push origin <current-branch>. If the branch has no upstream yet, use git push -u origin <current-branch>. NEVER force-push unless the user explicitly asks (and then prefer --force-with-lease).
  7. Report. State the commit hash, the message, exactly which files went in, and the push range (<old>..<new> branch -> branch).

Notes

  • If the push is rejected because the remote moved ahead, report it and ask before rebasing/merging — don't silently rewrite history.
  • This is the "ship it" counterpart to /wrapup (which finalizes the broader work product). Use /commitpush when you just want the staged work committed and on the remote.

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