commit

Enforce Conventional Commits formatting for Git commit messages.

Updated Oct 22, 2025

Search Tags:#git #commit #pre-commit #code-quality #version-control #conventional-commits #message-format

Ready to run

npx skills add https://github.com/jmfontaine/jmf-claude-plugins --skill commit-jmfontaine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/jmfontaine/jmf-claude-plugins/tree/main/plugins/git/skills/commit
Command: npx skills add https://github.com/jmfontaine/jmf-claude-plugins --skill commit-jmfontaine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent Git commit messages make history hard to read, complicate changelogs, and reduce traceability of changes.

Core Features & Use Cases

Enforces Conventional Commits formatting with allowed types: feat, fix, refactor, chore, docs, test, ci.
Guides when to add a body and how to structure subject lines for clear, actionable messages.
Supports workflows for creating, amending, squashing, or rewriting commits while maintaining an auditable history.

Quick Start

Apply conventional commits for every change, including a descriptive body when needed.

Frequently Asked Questions about commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What are conventional commits and why use them for git commit messages?▼

Conventional commits enforce consistent git commit messages using allowed types like feat, fix, and refactor. This formatting improves history readability, simplifies changelog generation, and enhances change traceability across project workflows.

How do I write a conventional commit message with a body?▼

To write a conventional commit message, start with an allowed type like feat or fix, write a clear actionable subject line, and add a descriptive body when needed to explain the change and maintain an auditable history.

Can I apply conventional commits when amending or squashing git commits?▼

Yes, you can apply conventional commits when amending or squashing git commits. The guidelines support diverse workflows including creating, rewriting, and squashing commits while maintaining traceability and readability of the history.

What commit types are allowed in conventional commits format?▼

Allowed commit types in the conventional commits format include feat, fix, refactor, chore, docs, test, and ci. These types categorize changes without using scopes to keep the version control history clean.

How do I fix inconsistent git commit history?▼

To fix inconsistent git commit history, enforce conventional commits formatting with allowed types and no scopes. This standardizes messages for creating, amending, or rewriting commits to improve traceability and readability.