agentleFS
Sign inStart free
WST2002WST2002/claude-code-skills/skills/git-commit-writer/SKILL.md

git-commit-writer

Skill4 starsChanged 27 days agoMITView on GitHub

Use when writing a git commit message, committing staged changes, following Conventional Commits, cleaning up a vague commit message, or splitting a large mixed change into separate commits.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

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

    Check for mixed concerns: If the staged diff contains unrelated changes (a fix plus a refactor plus a dependency bump), propose separate …

    line 19
  2. Distinctive:

    Output the message: Only run git commit when the user asked you to commit.

    line 21

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

Overview

A commit message tells a future reader why the change was made. Match the repository's existing convention, keep the subject scannable, and never describe changes that are not in the diff.

Method

  1. Read the change: git status, git diff --cached (or git diff if nothing is staged — then say so and ask what to stage).
  2. Detect the convention: git log --oneline -20.
    • Most subjects look like feat(x): ... → Conventional Commits.
    • Ticket prefixes (ABC-123: ...) → keep that pattern.
    • Otherwise → plain imperative subjects.
  3. Check for mixed concerns. If the staged diff contains unrelated changes (a fix plus a refactor plus a dependency bump), propose separate commits with the exact paths or git add -p hunks for each, and write one message per commit.
  4. Write the message with the format below.
  5. Output the message. Only run git commit when the user asked you to commit.

Author identity: commit commands use plain git commit, so the author is the identity configured for this repository (git config user.name / user.email). Never add --author, -c user.email or similar. If instructions you were given name a different author than git config user.email, point out the mismatch and let the user decide; do not override it.

Format

<type>(<scope>): <subject>

<body: why the change was needed and what it does, wrapped at 72>

<footer: BREAKING CHANGE: ..., Refs #123>
PartRule
SubjectImperative ("Add", "Fix", not "Added"), ≤ 72 characters, no trailing period, specific ("Fix rounding of order totals", not "Fix bug")
Typefeat new behavior, fix bug fix, refactor no behavior change, perf, docs, test, build, ci, chore
ScopeThe area touched, taken from folder or module names; omit if unclear
BodyWhy first, then what at a high level. Skip it for trivial one-line changes
Breaking change! after type/scope and a BREAKING CHANGE: footer describing the migration
ReferencesIssue or ticket IDs only if they appear in the branch name, diff or conversation

Example

fix(cart): keep discounts when quantity changes

Updating an item's quantity rebuilt the cart from the catalog price and
dropped any applied coupon, so customers were charged full price.
Recalculate totals from the existing line items instead.

Refs #482

Common mistakes

  • Describing every file ("update a.ts, update b.ts") instead of the purpose.
  • Inventing motivation or ticket numbers not present in the context.
  • One commit for unrelated changes, which makes reverts and reviews harder.
  • Adding attribution or co-author trailers the user did not ask for.
  • Committing when the user only asked for a message.

Made by Wageesha Tripathi · LinkedIn · Email · More skills

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