Make git commit

Skill zerocracy/zealot/skills/make-git-commit

Use this skill when the user wants to create a Git commit following the Conventional Commits specification.From its SKILL.md

Install

npx -y skills add zerocracy/zealot --skill make-git-commit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, 451 tokens by cl100k_base, as published. Nobody here has run it

Staging

Trust staged state. Commit straight from staged state, leaving edit, lint, test, and build aside. Stage files explicitly with paths user named.

Type

Respect Conventional Commits standard. Pick type from standard set. Hold to that standard set.

Description

Write description in imperative mood, lowercase. Use no trailing period. Keep description under 72 characters. Prepend ticket number with # to description. Do this when commit ties to known issue or pull request.

Breaking

Append ! after type or scope when commit introduces incompatible change. Add BREAKING CHANGE: footer when commit introduces incompatible change.

Body

Keep body to few short sentences. Explain motivation and visible effect. Omit body when subject says enough. Keep message free of restated diffs, file lists, and obvious summaries. Keep each commit to one related change.

Footers

Add Closes #<number> or Fixes #<number> footer only when needed. Add it only when host needs that token to auto-close ticket on merge.

Trailers

Keep every Co-authored-by: trailer free of Claude, Anthropic, and any agent. Leave author and committer identity as Git sets them. Keep message free of advertising trailers, signatures, and emoji. Keep message free of Generated with lines.

Safety

Run hooks and signing as configured unless user asked to bypass them. Confine work to one fresh local commit. Leave amend, rebase, force-push, and push aside.

Verify

Verify commit subject, body, footers, and file set after committing. Create new commit on top rather than amending when something is wrong.

Example

Input: staged src/parser.rs; ties to issue #214; user says "commit it"
git commit produces:
  fix: #214 reject trailing comma in arrays

  The array parser accepted a trailing comma, diverging from the
  JSON grammar. Tighten the lookahead so a stray comma now fails.

  Closes #214

Verified description leads with #214, stays under 72 chars,
lowercase, no trailing period; footer auto-closes the issue.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 1 of the 12 instructions most pr commit review skills give in 451 tokens

Counted across 1,055 of the 1,911 authors here whose files we hold, read 2026-09-06

Use conventional commit message formatin 150 of 1055, across 145 files
Announce skill usage at startin 78 of 1055
Use imperative mood for commit descriptionshere, and in 54 of 1055, across 51 files
Add directory to gitignore if not ignoredin 52 of 1055, across 41 files
Use imperative mood for commit subjectin 52 of 1055
Run tests to verify clean baselinein 42 of 1055, across 32 files
Push branch to originin 40 of 1055, across 38 files
Verify worktree directory is ignored before creationin 39 of 1055, across 32 files
Delete branches after mergingin 38 of 1055, across 30 files
Create worktree with new branchin 37 of 1055, across 32 files
Wrap body text at 72 charactersin 36 of 1055, across 34 files
Auto-detect and run project setupin 35 of 1055, across 27 files

Said here and by no other author read

Prepend ticket number to description
Append ! for incompatible changes
Explain motivation and visible effect in body
Run hooks and signing as configured

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.