mcpField
C
commit-message

commit-message

github.com/ujonDevelopment149 installsUpdated 6w ago
Repository

About commit-message

A skill for producing concise, intent-focused commit messages. It guides agents to inspect only the Git changes needed and format the result in a configured language.

Key features

  1. 01Locale-controlled message language
  2. 02Staged-change checks before writing
  3. 03Minimal diff inspection guidance
  4. 04Summary and Changes template
  5. 05Rules for concise, intent-led bullets

Use cases

  1. 01Writing a commit message after making changes
  2. 02Summarizing staged changes with unclear intent

Install

Copy the command and run it in a terminal.

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

After installing, type/commit-messagein Claude Code to confirm it loaded.

Bundled filesREADME.md

Details

From the project README

Commit Message

Settings

locale: en

Skill loaders strip YAML frontmatter, so settings live here at the top of the body. They are already in your context — never open this file to look them up. locale is the single source of truth for the message language: never infer it from the conversation, the user's messages, the repository, or prior commits.

Context Budget

Spend the least context needed to explain why the change was made, then stop.

  1. If you made the changes in this session you already know why — write the message directly. Use git status --short only to confirm what is actually staged.
  2. Otherwise start with git diff --staged --stat (git diff --stat when nothing is staged) to see the shape of the change.
  3. Open a real diff only for the files whose intent the stat leaves unclear, one path at a time: git diff --staged -- <path>.

Never dump a full diff you do not need, and skip lockfiles, generated output, and vendored paths.

Format

<one-line summary>

## Summary
<1-3 sentences on motivation and context>

## Changes
- <change 1>
- <change 2>

Rules

  • Write the one-line summary, the ## Summary body, and the ## Changes bullets in the configured locale.
  • Keep the ## Summary and ## Changes headers in English and title case.
  • Do not use prefix or scope tags such as feat:, fix:, or chore:.
  • Explain why the change was made, not only what changed.
  • Group related edits into one bullet by intent instead of enumerating every touched file. Keep ## Changes to the bullets that carry meaning, usually 2-6.

Example

Simplify login form validation logic

## Summary
Consolidated duplicated validation branches into one place to reduce maintenance overhead.

## Changes
- Merged email/password validation into a `validateLoginInput` helper
- Removed unused `legacyCheck` function
- Unified validation failure messages under the i18n dictionary

Comments

Markdown supported