agentleFS
Sign inStart free
ivanrvpereiraivanrvpereira/.agents/skills/auto/git-commit/SKILL.md

git-commit

Skill19 starsChanged 4 days agoApache-2.0View on GitHub

Read this skill before making git commits

  • Reads credentials

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 126 edited versions we read keep these.

  • 5

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

    Commit hygiene is never a reason to change the working tree.

    line 12
  2. Distinctive:

    Read git status and git diff.

    line 16
  3. Distinctive:

    If there is nothing to commit, say so and stop.

    line 17
  4. Distinctive:

    Add a body only when the change needs it: a blank line after the subject, then what changed and why, side effects, and trade-offs.

    line 24
  5. Distinctive:

    No breaking-change footers unless asked.

    line 25
  6. Very specific:

    If a hook fails, fix the cause and retry.

    line 30

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

Produce focused Conventional Commits that fit the repo's history.

Never undo work to shape history

Commit hygiene is never a reason to change the working tree. Use git reset or git restore --staged only to unstage. When changes are intertwined, split them only by file or by an obvious hunk; otherwise ask the user or commit them together with a clear message.

1. Stage

  1. Read git status and git diff. If the caller named files, globs, or instructions, limit scope to them and let the instructions shape the message.
  2. If there is nothing to commit, say so and stop. If unrelated or ambiguous files are present, ask which to commit.
  3. Stage only the intended files, one logical change per commit. Never stage files that look like secrets (.env, credentials, keys).

2. Write the message

  1. Match the repo's style and scopes: git log -n 50 --pretty=format:%s.
  2. Subject: <type>(<scope>): <summary>. Type is feat, fix, docs, refactor, chore, test, or perf; scope is optional; summary is imperative, at most 72 characters, no trailing period.
  3. Add a body only when the change needs it: a blank line after the subject, then what changed and why, side effects, and trade-offs. One sentence or bullet per line, never hard-wrapped. Issue references go at the bottom.
  4. No breaking-change footers unless asked. No sign-offs, co-author lines, or AI attribution.

3. Commit

  • git commit -m "<subject>" without a body; git commit -F <file> or a heredoc with one.
  • If a hook fails, fix the cause and retry. Never use --no-verify.
  • No --amend and no push unless the user asks.

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.

Reviews can't be read right now.

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