How do I install the Git Commit Convention skill?

Run npx skillmds@latest add edram/git-commit-convention 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 Convention skill do?

Reference for writing structured git commit messages. Use when asked to write a commit, generate a commit message, review commit style, or work with conventional commits format. It is listed under Coding & Dev Tools on SkillMD.

Is Git Commit Convention 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 Convention?

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 Convention free to use?

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

Who published Git Commit Convention?

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

Git Commit Convention by edram — Agent Skill

Name: Git Commit Convention
Author: edram

File contents

Conventional Commits 1.0.0 — a specification for writing commit messages that are human-readable and machine-parseable. Maps directly to Semantic Versioning: feat → MINOR bump, fix/perf → PATCH bump, breaking changes → MAJOR bump.

Only type and description are required; everything else is optional
Scope narrows the affected area: feat(auth):, fix(api):
Breaking changes use ! suffix or BREAKING CHANGE: footer (or both)
Footer tokens follow Git trailer convention
Default to English, but match the project's existing convention — check git log and follow whatever language recent commits use

<type>[optional scope][!]: <description>

[optional body]

[optional footer(s)]

Core

Topic	Description	Reference
Format	Full grammar, header/body/footer rules, length limits	core-format
Types	All 11 types with SemVer impact and when to use each	core-types

Features

Topic	Description	Reference
Breaking Changes	`!` syntax and `BREAKING CHANGE` footer — when and how	features-breaking
Footers	Token format rules, issue references, common tokens	features-footers
AI-Generated Changes	`Co-Authored-By` attribution for agent-authored commits — mandatory once it applies, fixed value format, and what not to add	features-ai-attribution

Frequently asked questions

Git Commit Convention