conventional-git-commit

Validate git commit messages against the Conventional Commits 1.0.0 specification.

11|2|Updated Feb 18, 2026

Search Tags:#automation #git #standardization #lint #conventional-commits #commit-messages

Ready to run

npx skills add https://github.com/the-perfect-developer/the-perfect-opencode --skill conventional-git-commit

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures every git commit message adheres to the Conventional Commits 1.0.0 standard, preventing drift and enabling consistent changelogs.

Core Features & Use Cases

Enforce type-driven commit messages (feat, fix, docs, etc.) with optional scopes.
Validate commit structure, including description, body, and footers, and reject non-conforming messages.
Use in code reviews, CI pipelines, or interactive git workflows to maintain a clean history.

Quick Start

Tell your AI to format the next commit message according to Conventional Commits 1.0.0 specification.

Frequently Asked Questions about conventional-git-commit

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

FAQPage Schema

How do I enforce conventional commit messages in git across manual commits and CI pipelines?▼

You can enforce conventional commit messages by validating the type, optional scope, breaking change markers, description, body, and footers against the Conventional Commits 1.0.0 specification, rejecting any non-conforming messages across manual commits, CLI tools, and automation to ensure consistent history.

What is the Conventional Commits 1.0.0 specification structure for git commit messages?▼

The Conventional Commits 1.0.0 specification structures git commit messages by enforcing a specific type, an optional scope, breaking change markers, a description, a body, and footers to maintain a clean and consistent version history.

How do I validate breaking change markers and footers in commit messages?▼

To validate breaking change markers and footers in commit messages, you enforce the Conventional Commits 1.0.0 specification, which checks these structural elements alongside the type, scope, description, and body to reject non-conforming messages.

Can I use conventional commits linting for code reviews and interactive git workflows?▼

Yes, you can use conventional commits linting in code reviews, CI pipelines, and interactive git workflows to validate type-driven commit messages and maintain a clean history by rejecting messages that do not conform to the specification.

Do I need any dependencies to standardize git commit messages with conventional commits?▼

No dependencies are required to standardize git commit messages with conventional commits, as the enforcement logic validates the commit structure directly without relying on external components or modules.