Commit

Skill jmfontaine/jmf-claude-plugins/plugins/git/skills/commit

Claude Plugins

Install

npx -y skills add jmfontaine/jmf-claude-plugins --skill 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

0 stars0 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.

What its author says it does

Copied from the file, not written here

Git commit guidelines. Use when creating, amending, squashing, or rewording git commits, staging files, or writing commit messages.

SKILL.md

1.9 KB, 358 tokens by cl100k_base, as published. Nobody here has run it

Git Commit Guidelines

Follow Conventional Commits with these overrides:

Allowed types: feat, fix, refactor, chore, docs, test, ci
Message format: <type>: <lowercase imperative description>
No scopes — do not use <type>(scope): form
Add body, separated by blank line, only when subject line insufficient

Pre-Commit Review

Before committing, review all staged and unstaged changes to determine if they should be split into multiple commits. Changes belong in separate commits when they have different types (e.g., feat + fix), affect unrelated areas, or serve distinct purposes.

If the user has not explicitly asked to split, suggest doing so and list the proposed commits. Proceed with a single commit only if all changes are logically cohesive.

Also check for changes made outside the current session (e.g., editor saves, other tools). If they are relevant to the commit, offer to include them. If they are unrelated, silently ignore them unless the user asks to include them.

New Commit vs. Amend

When changes closely follow a previous commit (e.g., a quick fix or forgotten file), evaluate whether amending the previous commit is more appropriate than creating a new one. Amending is preferable when the change corrects or completes the previous commit and that commit has not been pushed.

Never amend without the user's explicit approval. Present the two options (new commit vs. amend) and let the user decide.

Additional Guidelines

Always sign commits with git commit -S
Do NOT include AI co-authoring information
Do NOT use git -C <path> when the current directory is already the repository root

What ships with it

Read from the repository

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

Gives 0 of the 12 instructions most pr commit review skills give in 358 tokens

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-07

Use conventional commits formatin 127 of 888, across 115 files
Keep subject line under 72 charactersin 62 of 888, across 48 files
Delete branches after mergein 51 of 888, across 38 files
Use imperative mood in subject linein 51 of 888, across 42 files
Use imperative mood in commit messagesin 44 of 888
Verify directory is ignored before creating worktreein 43 of 888, across 12 files
Generate a conventional commit messagein 43 of 888
Add unignored worktree directories to gitignorein 42 of 888, across 10 files
Make atomic commitsin 39 of 888, across 27 files
Run tests before committingin 36 of 888, across 25 files
Verify clean test baselinein 35 of 888, across 9 files
Split unrelated changes into separate commitsin 35 of 888, across 30 files

Said here and by no other author read

omit scopes from commit messages
offer to include relevant external changes
silently ignore unrelated external changes
evaluate amending recent unpushed commits

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.