agentleFS
EclipterEclipter/agents/skills/sdlc/commit-message/SKILL.md

commit-message

Skill1 starsChanged 6 days agoMITView on GitHub

Write the commit message. Do not stage, commit, or push.

74 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pr-description, changelog and 8 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.
  • MicrosoftSkill

    pr-description

    Draft Nacelle PR titles, pull request descriptions, commit titles, commit descriptions, and squash commit messages. Use when asked for PR or commit wording, a branch summary, or a PR description that can be used in a commit. Omit validation sections from commit bodies and remove filler.

    Also in 9 projects that use this

  • HashiCorpSkill

    changelog

    Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.

    Also in 3 projects that use this

  • GitHubSkill

    refactor

    Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

    Also in 3 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 7 projects that use this

  • GoogleSkill

    grilling

    Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

    Also in 3 projects that use this

  • OpenAISkill

    brainstorming

    You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

    Also in 3 projects that use this

  • +1 more from google

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 63 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not quote secrets, tokens, or private keys.

    line 13
  2. Very specific:

    Add a scope in parentheses only when the repository already does, or when the subject is ambiguous without it.

    line 37
  3. Distinctive:

    Use imperative mood, as a continuation of "If applied, this commit will …".

    line 43
  4. Distinctive:

    Keep the whole line at most 50 characters, even when recent subjects are longer.

    line 46
  5. Distinctive:

    Write something that belongs in a changelog.

    line 48
  6. Distinctive:

    Add a body only when the subject does not explain why.

    line 50
  7. Very specific:

    If the repository has no commits yet, skip the log and use the default language and format.

    line 69

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

Principles

A repository commit convention (CONTRIBUTING, commitlint, .gitmessage) overrides the rules below.

Do not quote secrets, tokens, or private keys. If they appear in the diff, say they must not be committed instead of describing them as a normal change.

Message scope

  • Non-empty index: describe only staged changes. In one line, name what remains unstaged and will not be in this commit.
  • Empty index: describe the working tree and say that nothing is staged.
  • Several independent changes: one message per atomic commit, in apply order.

Format

Take the language and shape from recent commits when the style is consistent. Otherwise use English and Conventional Commits:

type: imperative summary

Why this exists, only when the subject does not already say it.

type: feat, fix, refactor, perf, docs, test, build, ci, chore, style, revert.

Add a scope in parentheses only when the repository already does, or when the subject is ambiguous without it. A breaking change uses type!: and a BREAKING CHANGE: trailer.

Subject line:

  • Use imperative mood, as a continuation of "If applied, this commit will …".
  • Describe the change to the system, not a file list or "update code".
  • Omit the trailing period.
  • Keep the whole line at most 50 characters, even when recent subjects are longer.
  • Write something that belongs in a changelog.

Add a body only when the subject does not explain why. Separate it from the subject with one blank line. Keep body lines under 72 characters where a break is possible (soft limit). Do not retell the diff or write "this commit".

Include trailers only when real: BREAKING CHANGE:, Fixes #n, Refs #n. Do not invent issue numbers.

Workflow

Inspect the changes

From the repository root, inspect in parallel:

  • git status --short
  • git diff --cached and git diff --cached --stat
  • git diff and git diff --stat, when the index is empty or unstaged changes remain
  • git log -20 --format='%s%n%b%n---'

If the repository has no commits yet, skip the log and use the default language and format. For a diff larger than about 2,000 lines, read --stat and sample key files instead of reading the whole diff.

Reply

First, one line: staged, the whole tree, or several commits. Then each message in its own fenced block, ready to paste into git commit. Nothing else.

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.