git-commit · thinkinaixyz — Claude Code skill: what it does, how to install
git-commit generates commit messages following Conventional Commits — type, scope, and subject. The agent reads staged changes via git diff --staged and proposes a message.
Apache-2.0 1 installs ★ 6,407 updated 2026-10-29
npx skills add ThinkInAIXYZ/deepchat --skill git-commit -a claude-codeWhat git-commit does
The skill teaches the agent to write commits in <type>(<scope>): <subject> format, where type is feat, fix, docs, refactor, or one of eight others. Subject line uses imperative mood, up to 50 characters, no period. Body wraps at 72 characters; footer references issues (Fixes #123) or marks breaking changes.
The agent runs git status or git diff --staged, analyses the changes, and builds a message. If you confirm, it executes git commit -m "message". The skill uses run_terminal_cmd, so git must be in PATH.
Fits projects where Conventional Commits is adopted and you want the agent to format commits according to the repository rules.
What it helps with
- generate a Conventional Commits message from staged changes
- pick the right commit type for code or documentation changes
- format issue references and breaking change markers in the footer
- automate commit writing in projects with a shared message standard
Example prompts for the agent
- Check staged changes and write a commit message
- Make a commit for staged files following Conventional Commits
- Build a commit message with type and scope for current changes
How to install git-commit
1Skills CLI (Vercel)
npx skills add ThinkInAIXYZ/deepchat --skill git-commit -a claude-code2Manually: put the files in place
~/.claude/skills/git-commit/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/git-commit/
1Skills CLI (Vercel)
npx skills add ThinkInAIXYZ/deepchat --skill git-commit -a codex2Manually: put the files in place
.agents/skills/git-commit/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ThinkInAIXYZ/deepchat --skill git-commit -a cursor2Manually: put the files in place
.cursor/skills/git-commit/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ThinkInAIXYZ/deepchat resources/skills/git-commit2Manually: put the files in place
.github/skills/git-commit/SKILL.md1Skills CLI (Vercel)
npx skills add ThinkInAIXYZ/deepchat --skill git-commit -a gemini-cli2Platform CLI
gemini skills install https://github.com/ThinkInAIXYZ/deepchat --path resources/skills/git-commitManually: put the files in place
.devin/skills/git-commit/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ThinkInAIXYZ/deepchat --skill git-commit -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about git-commit
How to install git-commit in Claude Code?
Run npx skills add ThinkInAIXYZ/deepchat --skill git-commit -a claude-code, then check the file ~/.claude/skills/git-commit/SKILL.md.
What does the git-commit skill do?
Generates commit messages following Conventional Commits: the agent reads changes via git diff --staged, picks a type (feat, fix, docs), writes the subject and optionally body with footer, then runs git commit -m after your confirmation.
Which commit types does git-commit support?
feat, fix, docs, style, refactor, perf, test, build, ci, chore. The skill selects the type based on what changed — a new feature, a bug fix, documentation, or build configuration.
Source text
SKILL.md · Apache-2.0
---
name: git-commit
description: Generate well-formatted git commit messages following conventional commit standards
allowedTools:
- run_terminal_cmd
---
# 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
© ThinkInAIXYZ · Apache-2.0 · ThinkInAIXYZ/deepchat
Similar skills
All skills for Git and GitHub →git-commit by other authors comes first.