Stats
Actions
Tags
From git
Git commit guidelines. Use when creating, amending, squashing, or rewording git commits, staging files, or writing commit messages.
How this skill is triggered — by the user, by Claude, or both
Slash command
/git:commitThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Follow Conventional Commits with these overrides:
Follow Conventional Commits with these overrides:
feat, fix, refactor, chore, docs, test, ci<type>: <lowercase imperative description><type>(scope): formBefore 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.
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.
git commit -Sgit -C <path> when the current directory is already the repository rootnpx claudepluginhub jmfontaine/jmf-claude-plugins --plugin gitGuides git commits with atomic change analysis, conventional commit messages, and interactive staging options. Flags non-atomic commits and suggests splits for better maintainability.
Analyzes Git changes, groups staged/unstaged files into logical commits by feature/type/scope, and executes them one-by-one using conventional commit format.
Drafts Conventional Commits messages for staged git changes. Proposes a type-scoped subject line, waits for user approval, then commits.