git-commit

Enforce Conventional Commits formatting with scopes and imperative subjects.

69|6|Updated Dec 21, 2025

Search Tags:#git #scope #commit-message #conventional-commits #subject #project-conventions

Ready to run

npx skills add https://github.com/fvadicamo/dev-agent-skills --skill git-commit-fvadicamo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/fvadicamo/dev-agent-skills/tree/main/skills/git-commit
Command: npx skills add https://github.com/fvadicamo/dev-agent-skills --skill git-commit-fvadicamo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creates git commits following Conventional Commits format, enabling consistent project history and easier code reviews by enforcing scope, subject structure, and project-specific conventions from CLAUDE.md.

Core Features & Use Cases

Enforces Conventional Commits format across commits, ensuring consistency in type, scope, and subject.
Requires explicit scope and present-tense imperative subject, with a maximum subject length and avoidance of generic messages.
Aligns commits with repository-specific conventions defined in CLAUDE.md to maintain project standards.

Quick Start

Stage changes with git add and commit using a Conventional Commits message that includes a type, a scope in parentheses, and a concise subject.

Frequently Asked Questions about git-commit

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

FAQPage Schema

How do I enforce Conventional Commits formatting for git commits?▼

To enforce Conventional Commits formatting, this Skill validates commits against rules requiring an explicit scope, present-tense imperative subject, maximum 50 characters, no trailing periods, and alignment with project-specific CLAUDE.md conventions to ensure consistent history.

What is the correct format for a conventional commit message with a scope?▼

A conventional commit message requires a type, a scope in parentheses, and a concise subject. The subject must use present-tense imperative mood, stay under 50 characters, contain no trailing periods, and avoid generic messages.

How do I avoid generic git commit messages across multiple repositories?▼

Avoid generic git commit messages by applying formatting rules that reject vague subjects, require an explicit scope, and align commits with repository-specific conventions defined in CLAUDE.md to maintain project standards.

Can I use CLAUDE.md to define project-specific conventions for commit messages?▼

Yes, you can use CLAUDE.md to define project-specific conventions. The Skill aligns commits with repository-specific rules in CLAUDE.md to maintain project standards while enforcing Conventional Commits format.

Why does my conventional commit subject fail validation when staging changes?▼

Your conventional commit subject fails validation if it lacks an explicit scope, exceeds 50 characters, uses non-imperative mood, includes trailing periods, or contains generic messages instead of concise descriptions.

Do I need to stage changes with git add before enforcing conventional commit rules?▼

Yes, stage changes with git add before committing. The Skill is applicable during everyday development tasks such as staging changes, creating commits, and documenting work across multiple repositories using Conventional Commits format.