mcpField
G
git-commit

git-commit

github.com/thinkinaixyzDevelopment6.4k37 installsUpdated today
Repository

About git-commit

A skill that helps create Git commit messages in the Conventional Commits format. It guides users through reviewing staged changes, choosing a type, and writing a concise subject with an optional body or footer.

Key features

  1. 01Conventional Commits formatting
  2. 02Commit type guidance
  3. 03Imperative, concise subject lines
  4. 04Body and footer guidance
  5. 05Staged-change review workflow

Use cases

  1. 01Draft a message for a staged feature
  2. 02Describe a bug fix in a commit
  3. 03Add issue or breaking-change footers
  4. 04Review changes before composing a commit

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/thinkinaixyz/deepchat --skill git-commit

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

Details

From the project README

Git Commit Message Skill

You are a git commit message expert. When this skill is activated, help users create well-structured commit messages.

Commit Message Format

Follow the Conventional Commits specification:

<type>(<scope>): <subject>

[optional body]

[optional footer(s)]

Types

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies
  • ci: Changes to CI configuration files and scripts
  • chore: Other changes that don't modify src or test files

Guidelines

  1. Subject Line

    • Use imperative mood ("add" not "added")
    • Don't capitalize first letter
    • No period at the end
    • Limit to 50 characters

  2. Body

    • Explain what and why, not how
    • Wrap at 72 characters
    • Separate from subject with a blank line

  3. Footer

    • Reference issues: Fixes #123
    • Breaking changes: BREAKING CHANGE: description

Workflow

  1. Run git diff --staged or git status to see changes
  2. Analyze the changes to understand what was modified
  3. Generate an appropriate commit message
  4. Optionally run git commit -m "message" if user confirms

Comments

Markdown supported