agentleFS
Sign inStart free
nortonxnortonx/ai-tooling-free/skills/create-commit-message/SKILL.md

create-commit-message

Skill1 starsChanged 59 days agoMITView on GitHub

Produce a single ready-to-paste conventional commit message with a `<type>: ` prefix from current git changes, invoke only when explicitly asked to write/draft/create a commit message.

3 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

9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 8

    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:

    Read staged changes: git diff --cached

    line 10
  2. Distinctive:

    Read unstaged changes: git diff

    line 11
  3. Distinctive:

    Read recent commits for style match: git log --oneline -10

    line 12
  4. Distinctive:

    If both diffs are empty, stop and say "nothing to commit".

    line 13
  5. Distinctive:

    Read the current branch name (git branch --show-current).

    line 14
  6. Very specific:

    If the branch name contains an issue id (e.g.

    line 25
  7. Distinctive:

    Use imperative mood: "add feature" not "added feature"

    line 30
  8. Distinctive:

    If changes span multiple concerns, suggest splitting into separate commits

    line 31
  9. Distinctive:

    If quotes are to be used, use single quotes always

    line 34

“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

Commit message

Steps

  1. Read staged changes: git diff --cached
  2. Read unstaged changes: git diff
  3. Read recent commits for style match: git log --oneline -10
  4. If both diffs are empty, stop and say "nothing to commit".
  5. Read the current branch name (git branch --show-current). If it contains an issue/ticket id, reference it per the repo convention visible in git log.

Output format

<type>(<optional scope>): <short summary in imperative mood, max 72 chars>

<optional body: what changed and why, wrapped at 72 chars, splitted as bullet items>

Where <type> is one of: feat, fix, refactor, docs, test, chore, perf, ci If the branch name contains an issue id (e.g. 123 in feat/123-add-login), include it the way recent commits in git log do (e.g. (#123) suffix); omit it otherwise.

Rules

  • Be concise: focus on the "why", not the "what" (the diff shows the what)
  • Use imperative mood: "add feature" not "added feature"
  • If changes span multiple concerns, suggest splitting into separate commits
  • Output only the message, ready to copy-paste
  • Message should be for one commit only. Do not split into more than one commit
  • If quotes are to be used, use single quotes always

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