mcpField
C
commit

commit

github.com/angusfretwellDevelopment192 installsUpdated 4d ago
Repository

About commit

A skill for composing Conventional Commits from a Git diff. It guides developers through classifying changes, writing commit messages, and committing without bypassing checks.

Key features

  1. 01Inspect staged or unstaged changes
  2. 02Classify type, scope, and description
  3. 03Add explanatory body and issue footer
  4. 04Handle breaking changes
  5. 05Check for secrets before committing

Use cases

  1. 01Prepare a commit message from a completed change
  2. 02Separate unrelated changes into commits
  3. 03Document an issue reference or breaking change

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/angusfretwell/skills --skill commit

After installing, type/commitin Claude Code to confirm it loaded.

Details

From the project README

Write every commit in Conventional Commits format: <type>(scope): <description>, then an optional body and footer.

Steps

  1. Read the diff. Run git status and git diff --staged (fall back to git diff when nothing is staged).
  2. Classify. Choose the type (feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert), the scope (the affected area, omitted when the change is broad), and a description — one imperative-mood line under 72 characters. Each of the three must trace to a specific change in the diff. If the diff holds more than one unrelated change, commit them separately.
  3. Compose. Assemble the subject line. Add a body — the why, and what a reader can't see from the diff — when the change isn't self-evident, and a footer (Closes: <id>, Refs: <id>) when an issue applies. Signal a breaking change with ! (feat(api)!: require verified email), or a BREAKING CHANGE: footer when the break needs explaining.
  4. Commit. Stage the intended files — if they contain secrets or credentials, stop and flag it instead. Run git commit and let hooks run; if one fails, fix the cause or report it.

Rewriting shared history or bypassing checks — --force, reset --hard, --no-verify, git config edits — happens only when the user explicitly asks.

Comments

Markdown supported