agentleFS
Sign inStart free
DoTrungHuyDoTrungHuy/skillmeter/skills/original/git-commit-writer/SKILL.md

git-commit-writer

Skill2 starsChanged 2 months agoMITView on GitHub

Drafts Conventional Commits messages from staged diffs, choosing type and scope from the actual change shape rather than the request wording.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. mergisi/awesome-openclaw-agents★ 4.1ksame name
    2. WST2002/claude-code-skills★ 4same name
    3. Tejas9406/vibe-coding-os★ 1same name
    4. poorvith-mp/skills-developer★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 4

    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:

    Write commit messages that reviewers can scan.

    line 13
  2. Distinctive:

    Before committing, when the user asks for a commit message or says "commit this".

    line 17
  3. Distinctive:

    Run git diff --cached --stat to see the change shape.

    line 21
  4. Distinctive:

    Write a subject line under 72 characters describing the why, then a body if the diff mixes concerns.

    line 23

“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

Conventional Commit Drafter

Write commit messages that reviewers can scan.

When to use

Before committing, when the user asks for a commit message or says "commit this".

Steps

  1. Run git diff --cached --stat to see the change shape.
  2. Pick the type: feat, fix, docs, refactor, test, chore.
  3. Write a subject line under 72 characters describing the why, then a body if the diff mixes concerns.

Example

feat(api): retry idempotent payments on 409

Payment submit can race on gateway timeouts; reuse the idempotency key.

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