agentleFS
TsukiNi22TsukiNi22/ai-utils/skills/git/git-commit/SKILL.md

git-commit

Skill1 starsChanged 3 days agoMITView on GitHub

Make the local commit(s) of the diff that currently exists in the repository, the way Tsukini does it in his repositories - the pending changes grouped in logical commits, each message = its title only (type(scope): message, one short line, no body, no description, no Co-Authored-By), local only (never pushed). Use whenever the user asks to commit the current changes / the diff / "fais le commit", "commit tout", "commit les modifs locales".

  • Reads credentials
  • Commits and pushes

182 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use git-pr, github-pr-create 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.
  • klauswgSkill

    git-pr

    Prepare, review, publish, or update a complete GitHub pull request for the current repository, including local commit readiness, safe push strategy, semantic title validation, repository-native PR templates, issue linking, and checks verification. Use when the user asks to draft, create, submit, publish, open, or update a pull request. Always require the user to review and explicitly approve the exact final PR before any push or GitHub write.

    Also in 11 projects that use this

  • mjun0812Skill

    github-pr-create

    Pull Requestを作成するSkill。現在のbranchからpull requestを作成する。言語指定可能。 ユーザーが「PR作って」「pull request作成して」のように依頼したら使うこと。

    Also in 3 projects that use this

  • MicrosoftSkill

    git-branch

    Branch management for implementation. Use when you need to create a branch, switch branches, checkout, or verify branching strategy before implementing code. Do not use for commits (use git-commit), pull requests (use pull-request), or advanced git operations (rebase, merge).

    Also in 4 projects that use this

  • klauswgSkill

    git-issue

    Prepare, review, create, or update evidence-based GitHub issues for the current repository with duplicate detection, repository-native templates, valid labels, and post-publication verification. Use when the user asks to draft, file, submit, publish, edit, or refine a GitHub issue, bug report, feature request, performance issue, or technical proposal. Always require the user to review and explicitly approve the exact final issue before any GitHub write.

    Also in 3 projects that use this

  • gologo13Skill

    git-push

    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.

    Also in 6 projects that use this

  • GoogleSkill

    github-pr-review

    Review a GitHub pull request and leave inline comments in a natural human reviewing voice, indistinguishable from comments typed by hand on the GitHub web UI. Deliberately bounded to defects a reader can settle by looking at the anchored line, rather than a deep audit, so every comment is cheap for the author to check. Scales to 2-20 comments by PR size, parallelises analysis across sub-agents, drafts for approval, then posts individually with human pacing. Use when the user says "review this PR", "review PR 123", pastes a github.com/.../pull/N link, or asks for comments on a pull request. Don't use for reviewing local uncommitted changes or a diff against a branch (use the `review` skill for that).

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 141 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the real diff (\git diff, \git diff --cached) of what is not obvious.

    line 23
  2. Very specific:

    Never stage what must not be versioned: build trees, logs, caches, .env / keys / tokens, big binaries, scratch folders (ex: …

    line 24
  3. Very specific:

    No Co-Authored-By, no "Generated with", no AI mention: Only exception: a repository whose own instructions require the trailer (the …

    line 48
  4. Distinctive:

    Never amend, rebase, reset or rewrite an existing commit unless asked.

    line 54

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

Commit the current diff (local)

The request to run this skill is the explicit request to commit (the global "never commit unprompted" rule is satisfied); it is not a request to push, tag, release or open a PR.

Load git-conventions first (message format, types, scopes, CI keywords): it is the source of truth, and /git routes here.

1. Look at the diff

\git status --short
\git diff --stat            # unstaged
\git diff --cached --stat   # already staged
\git log --oneline -10      # the style of the repository, scopes already used
  • Read the real diff (\git diff, \git diff --cached) of what is not obvious; untracked files are read too.
  • Never stage what must not be versioned: build trees, logs, caches, .env / keys / tokens, big binaries, scratch folders (ex: .claude-cluster*). If it looks like noise and is not in .gitignore, ask (or leave it out and say so); never add it to .gitignore on your own.
  • Nothing to commit -> say it and stop.

2. Group

  • One logical change per commit (git-conventions): split by purpose, not by file count - a fix, a feature, its docs, the tests, a pure rename / reformat are separate commits when they can stand alone.
  • The CHANGELOG update is its own commit (docs(CHANGELOG): ...) and comes last.
  • A change that only makes sense together stays together. When a file mixes two purposes, split it with git add -p only if the hunks are clean; otherwise commit it with the dominant purpose.
  • Order the commits so each one builds (dependencies first, docs / changelog last).
  • A very large or ambiguous diff: show the planned commits (title + files) in one short list and go on unless the split is really ambiguous (then ask once).

3. Commit

For each group, stage by path (never git add -A / .), check what is staged, commit:

\git add -- <paths>
\git diff --cached --stat
\git commit -m "<type>(<scope>): <message>"
  • Message = the title only: one short line in English, the global recap of the group, in the style of the recent log. No body, no description, no bullet list, no second -m.
  • No Co-Authored-By, no "Generated with", no AI mention. Only exception: a repository whose own instructions require the trailer (the ai-utils repository, per its CLAUDE.md): then exactly that trailer, nothing else.
  • A CI keyword ([build] / [release] / [ignore]) only when the repository's workflows use them and the user asked for it.
  • A hook that fails (xstyle pre-commit, formatter): fix the cause, restage, commit again (a new commit, no --amend of a commit that failed). Never --no-verify.
  • Never amend, rebase, reset or rewrite an existing commit unless asked.

4. Report

\git log --oneline -<n> of the new commits and \git status --short (what is left uncommitted and why). Then the push command as a suggestion only (\git push), never run.

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.