git-commit skill
✓ VerifiedGenerate well-formatted git commit messages following the Conventional Commits specification.
- GitHub stars
- 6,388
- Files
- 1
- Last commit
- Nov 11, 2026
- License
- Apache-2.0
- Allowed tools
- —
What does the git-commit skill do?
git-commit generates well-formatted git commit messages following the Conventional Commits specification.
Summary generated from the skill's SKILL.md.
About the git-commit skill
Writing standardized commit messages for version control is the primary function of this tool. Developers use it to transform code changes into structured messages that adhere to the Conventional Commits specification. When an agent loads this skill, it can analyze staged changes by running terminal commands like git diff --staged or git status to understand exactly what was modified in the codebase.
The skill produces messages categorized by specific types such as feat, fix, docs, or refactor, including optional bodies and footers. It follows strict formatting rules, such as using the imperative mood for subject lines, limiting subjects to 50 characters, and wrapping body text at 72 characters. Once a message is generated and approved, the agent can execute the git commit command to finalize the process.
What an agent can do with it
- 1Generate conventional commit messagesCreate a structured commit message based on the current staged changes in a repository.
- 2Analyze staged code changesExamine the differences in the staging area to determine the intent of the code modifications.
- 3Automate the commit processFinalize a code commit using a generated message after receiving user confirmation.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the git-commit skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the git-commit skill in Claude Code
~/.claude/skills/git-commit/SKILL.md
$ npx degit ThinkInAIXYZ/deepchat/resources/skills/git-commit ~/.claude/skills/git-commitInstall the git-commit skill in Claude Code (project)
.claude/skills/git-commit/SKILL.md
$ npx degit ThinkInAIXYZ/deepchat/resources/skills/git-commit .claude/skills/git-commitInstall the git-commit skill in Codex
~/.agents/skills/git-commit/SKILL.md
$ npx degit ThinkInAIXYZ/deepchat/resources/skills/git-commit ~/.agents/skills/git-commitInstall the git-commit skill in Gemini CLI
~/.gemini/skills/git-commit/SKILL.md
$ npx degit ThinkInAIXYZ/deepchat/resources/skills/git-commit ~/.gemini/skills/git-commitInstall the git-commit skill in Claude.ai
npx degit ThinkInAIXYZ/deepchat/resources/skills/git-commit git-commit && zip -r git-commit.zip git-commit # claude.ai → Customize → Skills → + → Create skill → Upload a skill → git-commit.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work · What to fix for more points
- Source repository linked and reachablethinkinaixyz/deepchat/resources/skills/git-commit is public and reachablegithub.com/thinkinaixyz/deepchat/tree/HEAD/resources/skills/ ↗Pass
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-11github.com/thinkinaixyz/deepchat/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/thinkinaixyz/deepchat/blob/HEAD/resources/skills/ ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/thinkinaixyz/deepchat/blob/HEAD/resources/skills/ ↗Pass
- SKILL.md follows the Agent Skills formatthe description does not say when to use the skillgithub.com/thinkinaixyz/deepchat/blob/HEAD/resources/skills/ ↗Finding
SKILL.md
View on GitHubGit 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
- Reference issues:
Workflow
- Run
git diff --stagedorgit statusto see changes - Analyze the changes to understand what was modified
- Generate an appropriate commit message
- Optionally run
git commit -m "message"if user confirms
Files in this skill
1git-commit skill questions
How do I install the git-commit skill in Claude Code?
Run npx degit ThinkInAIXYZ/deepchat/resources/skills/git-commit ~/.claude/skills/git-commit. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the git-commit skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What format does this skill use for commit messages?
The skill follows the Conventional Commits specification, including type, scope, subject, and optional body or footer.
What are the rules for the commit subject line?
The subject line should use the imperative mood, avoid capitalizing the first letter, have no trailing period, and be limited to 50 characters.
How does the agent identify what changes need to be committed?
The agent runs git diff --staged or git status to analyze the modifications.