agentleFS
Sign inStart free
PradnyeshpPradnyeshp/Claude-Skills/.claude/skills/commit-message/SKILL.md

commit-message

Skill2 starsChanged 4 months agoMITView on GitHub

Generate a conventional commit message from staged git changes. Use when the user asks to commit, write a commit message, says "commit this", "what should the commit message be", or "prepare a commit".

62 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use code-review, grilling and 6 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.
  • 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

  • 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

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

  • +2 more from google

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 2

    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:

    type: must be one of: feat, fix, refactor, chore, docs, test, style, perf, ci, build

    line 29
  2. Distinctive:

    If changes span multiple logical units, suggest splitting into separate commits and show each proposed message.

    line 33
  3. Distinctive:

    If there are no staged changes, tell the user to stage files first with git add.

    line 34

“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

Staged changes

!git diff --cached --stat

!git diff --cached

Instructions

Generate a commit message for the staged changes above following the Conventional Commits specification.

Format

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

<body>

Rules

  1. type must be one of: feat, fix, refactor, chore, docs, test, style, perf, ci, build
  2. scope is the primary area affected (e.g., auth, api, ui). Auto-detect from the changed file paths. If the user passed an argument, use $ARGUMENTS as the scope instead.
  3. subject is imperative mood, lowercase, no period, under 50 characters
  4. body is optional — include only when the "what" isn't obvious from the subject. Wrap at 72 characters. Explain why, not what.
  5. If changes span multiple logical units, suggest splitting into separate commits and show each proposed message.
  6. If there are no staged changes, tell the user to stage files first with git add.

Output

Print ONLY the commit message — no explanation, no markdown fences. If suggesting a split, use numbered sections.

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