Git Commit

This one analyzes your staged git changes and writes commit messages that follow the Conventional Commits spec. It checks your diff, figures out whether you're adding a feature or fixing a bug or just updating docs, then formats everything properly with the right type prefix, a concise subject line in imperative mood, and optional body text explaining the why. Honestly, it's most useful when you've made changes across multiple files and need help synthesizing a clean message that captures the intent without just listing every file touched. It can also execute the commit for you once you approve the message, though I'd probably review it first until you trust its judgment on your codebase.

GitHub stars: 6K
last updated: Jun 11, 2026

View on GitHub

Install

$ npx -y skills add thinkinaixyz/deepchat --skill git-commit --agent claude-code

Installs into .claude/skills of the current project.

Files

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