mcpbeat

Git Commit

thinkinaixyz/git-commit

Generate well-formatted git commit messages following conventional commit standards

405 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
6187
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/ThinkInAIXYZ/deepchat --skill git-commit

The instruction itself

5 sections, as written by the author

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

  • Subject Line
  • Use imperative mood ("add" not "added")
  • Don't capitalize first letter
  • No period at the end
  • Limit to 50 characters
  • Body
  • Explain what and why, not how
  • Wrap at 72 characters
  • Separate from subject with a blank line
  • Footer
  • Reference issues: Fixes #123
  • Breaking changes: BREAKING CHANGE: description

Workflow

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

How to use it

Copy the folder

Take thinkinaixyz/git-commit from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.