mcpField
G
git-commit-format

git-commit-format

github.com/somnio-softwareDevelopment8115 installsUpdated 6d ago
Repository

About git-commit-format

git-commit-format is a skill that turns change descriptions into Git commit messages for developers using Conventional Commits. It produces a title and English bullet-point description, with guidance on types and formatting.

Key features

  1. 01Generate commit messages from change descriptions
  2. 02Follow Conventional Commits title syntax
  3. 03Write English description bullets based on changes
  4. 04Guide commit type selection
  5. 05Omit AI attribution and other trailers

Use cases

  1. 01Write a commit message for a feature change
  2. 02Format a title for a bug fix
  3. 03Summarize code changes in commit bullets

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/somnio-software/somnio-ai-tools --skill git-commit-format

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

Details

From the project README

Git Commit Format Skill

Generates a commit message (title + description) from a description of changes.

Conventions

Commit Title

Follows Conventional Commits spec:

{type}({optional scope}): {short imperative description}
  • Types: feat, fix, chore, refactor, docs, style, test, perf, ci, build, revert
  • Use imperative mood: "add", "fix", "remove" — not "added", "fixed", "removed"
  • Max ~72 characters
  • All lowercase except proper nouns
  • No period at the end
  • Example: feat(auth): add biometric login support
Commit Description

Bullet list using past tense action words:

* Fixed ...
* Added ...
* Changed ...
* Removed ...
  • Only include bullets that apply to the actual changes
  • Keep each bullet concise and specific
  • Allowed verbs: Fixed, Added, Changed, Removed, Updated, Refactored, Migrated, Deprecated
  • Always in English
  • Never include Co-Authored-By, Signed-off-by, or any trailer attributing the commit to an AI agent or tool

Type Selection Guide

TypeWhen to use
featNew functionality
fixBug fix
refactorCode change with no behavior change
choreConfig, deps, tooling, maintenance
testAdding or updating tests
docsDocumentation only
styleFormatting, whitespace
perfPerformance improvement
ciCI/CD changes
buildBuild system changes
revertReverting a previous commit

If the changes span multiple concerns, suggest splitting into separate commits.

Output Format

feat(flutter): upgrade Flutter SDK to v3.19

* Updated Flutter SDK version to 3.19
* Changed minimum iOS deployment target to 14.0
* Fixed deprecated API usages after upgrade
* Removed unused legacy plugins

The commit message must end after the bullet list. Do not append any Co-Authored-By, Signed-off-by, or AI attribution trailers.

Examples

User: "I upgraded Flutter and had to fix some deprecated APIs and update the iOS target"

feat(flutter): upgrade Flutter SDK to v3.19

* Updated Flutter SDK version to 3.19
* Changed minimum iOS deployment target to 14.0
* Fixed deprecated API usages after upgrade

User: "Fixed a crash on login when the user has no internet"

fix(auth): handle login crash when offline

* Fixed crash on login screen when no internet connection is available
* Added offline error state to login flow

Comments

Markdown supported