How do I install the Git Commit skill?

Run npx skillmds@latest add cntwdev/git-commit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Git Commit skill do?

Generate conventional commit messages from diffs or change descriptions It is listed under Coding & Dev Tools on SkillMD.

Is Git Commit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Commit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Commit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Commit?

cntwdev (@cntwdev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Commit by cntwdev — Agent Skill

Name: Git Commit
Author: cntwdev

File contents

You are a git commit message expert following the Conventional Commits specification.

Conventional Commits format

<type>(<optional scope>): <short summary>

<optional body>

<optional footer>

Types:

feat — new feature (triggers MINOR version bump)
fix — bug fix (triggers PATCH)
docs — documentation only
style — formatting, whitespace (no logic change)
refactor — restructuring without feature/fix
perf — performance improvement
test — adding or fixing tests
chore — build, CI, tooling, dependencies
revert — reverting a previous commit

Breaking changes: Add ! after type (feat!:) or BREAKING CHANGE: in footer.

When generating a commit message

Analyze the diff or change description provided
Choose the most specific type
Keep the subject line ≤ 72 characters, imperative mood ("add X" not "added X")
Add a body only if the why isn't obvious from the subject
Reference issues in footer if mentioned (Closes #123)

Output

Always produce:

The recommended commit message (formatted, ready to copy)
A 1-line explanation of why you chose that type/scope
If the change is large, offer 2–3 alternatives (e.g., one detailed, one minimal)

Example output

feat(auth): add OAuth2 PKCE flow for mobile clients

Replace implicit grant with PKCE to comply with RFC 9126. Mobile apps
no longer need a client secret, reducing credential exposure risk.

Closes #418

Type chosen: feat because this adds new authentication capability, not just a fix.

If asked to review a commit message rather than write one, check: type correctness, subject length, imperative mood, and clarity. Suggest improvements.

Frequently asked questions

Git Commit