Conventional Commits

Use this capability whenever you write a Git commit message or title a pull request. It gives you the Conventional Commits v1.0.0 contract — a header shape release tooling can parse and a human can scan in git log --oneline — together with a runnable validator that catches a malformed header before it lands. The normative rules below are summarized from the specification, so applying them needs no network fetch.

This skill is self-contained: it names no repository-specific file or layout, and the contract it carries is the same wherever it is installed. Where a host project narrows the rules — a restricted type list, a mandatory scope, a commit trailer its own tooling reads — follow the host's convention on that point and keep the structure below.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Overall Format

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

[optional body]

[optional footer(s)]

Guidelines: