agentleFS
Sign inStart free
abigaylehabigayleh/claude-workflow-plugin/skills/commit-message/SKILL.md

commit-message

Skill0 starsChanged 46 days agoMITView on GitHub

Use when making a git commit — when to commit, and the required single-line message format. Enforced by a PreToolUse hook that rejects bodies, multiple -m flags, and missing type prefixes.

62 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 7 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

  • 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

  • MicrosoftSkill

    grill-with-docs

    Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 4 projects that use this

  • +2 more from google

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 3

    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. Very specific:

    After a logically complete change that has passed the diff-review skill.

    line 14
  2. Distinctive:

    Never commit broken or half-finished code.

    line 16
  3. Distinctive:

    Always to a feature branch, never the base.

    line 17
  4. Distinctive:

    If it rejects a commit, fix the message.

    line 51

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

Full rules: ${CLAUDE_PLUGIN_ROOT}/conventions/git.md.

When to commit

  • After a logically complete change that has passed the diff-review skill.
  • One commit per coherent change — don't bundle unrelated work.
  • Never commit broken or half-finished code.
  • Always to a feature branch, never the base. A hook blocks the latter.

Format

A single line. type: summary. No body, ever.

git commit -m "feat: add password reset flow"
  • Types: build chore ci docs feat fix perf refactor revert style test
  • Summary: imperative mood, lowercase, no trailing period. Aim for ~50 characters, hard ceiling 72.
  • Optional scope: fix(parser): handle empty input. Breaking change marked with ! before the colon: feat(api)!: drop v1 endpoints.
  • No body, no bullets, no AI attribution or co-author footers.

Why no body: a body is where a change that couldn't be summarized goes to hide. If one line won't cover it, the commit is doing too much — split it.

Examples

  • feat: add password reset flow
  • fix: handle null response from user endpoint
  • refactor: extract shared fetch logic
  • chore: bump prisma to 5.14

Enforcement

hooks/check-commit-msg.py blocks any git commit that carries a body, uses multiple -m flags, sources the message from a file or heredoc, omits -m, or lacks a valid type prefix — and any commit that targets the base branch.

If it rejects a commit, fix the message. Don't work around the hook.

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