git-commit

Validate Git commit messages against conventional commit formatting rules.

Updated Jan 22, 2026

Search Tags:#git #commit #formatting #lint #version-control #conventional-commits

Ready to run

npx skills add https://github.com/ketronkowski/skills --skill git-commit-ketronkowski

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps development teams ensure every git commit follows the conventional commit format, enabling clearer history, easier release notes, and automated changelog generation.

Core Features & Use Cases

Validation: Verifies commit message structure against the conventional commit pattern and suggests corrections.
Guidance: Provides examples for common types like feat, fix, docs, chore.
Automation Ready: Compatible with pre-commit hooks or CI pipelines to enforce standards across repositories.

Quick Start

Use this skill before you commit to validate and format your message into a conventional commit. Example: feat: add user authentication.

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 commit formatting in a CI pipeline?▼

To enforce conventional commit formatting in a CI pipeline, validate commit messages against the conventional pattern before merges. This ensures lowercase descriptions after the colon and concise summaries across automated workflows.

What is the conventional commit format for git commit messages?▼

The conventional commit format for git requires specific types like feat, fix, docs, or chore, followed by a colon and a lowercase description. This structure enables clearer history and automated changelog generation.

How do I validate a git commit message before merging?▼

You validate a git commit message by checking its structure against the conventional commit pattern and suggesting corrections. This verifies the commit type and ensures concise summaries before merges.

Can I use a pre-commit hook to validate conventional commits?▼

Yes, you can use a pre-commit hook to validate conventional commits. This automation-ready approach enforces commit message standards directly within your local repository workflow before finalizing changes.

Why should my development team enforce conventional commit types?▼

Enforcing conventional commit types helps development teams ensure every git commit follows a standardized format, enabling clearer project history, easier release notes, and automated changelog generation.