conventional-commits

You can generate a conventional commit message from staged git changes by providing the staged diff; the Skill analyzes it and produces a single spec-compliant header with an appropriate type, optional scope, and concise description per the v1.0.0 format.

Validating existing git commit messages involves checking your commit text against the v1.0.0 reference rules; the Skill returns a list of specific violations and provides a faithful compliant rewrite of any non-compliant message.

The Conventional Commits v1.0.0 format structures commit headers with a type, optional scope, and description; a BREAKING CHANGE footer is required when changes introduce incompatible API modifications, which the Skill adds only when necessary.

Yes, you can rewrite non-compliant commit messages to follow the specification; the Skill evaluates existing commit text, identifies formatting violations against the v1.0.0 reference, and outputs a faithful compliant rewrite.

No external dependencies or tools are required to validate commit messages; the Skill uses an included v1.0.0 reference for exact validation rules and rewrite patterns, functioning standalone without additional packages.

The best way to create a commit message from a user-provided summary is to supply your text summary; the Skill generates one best Conventional Commit message with an appropriate type, optional scope, and concise description compliant with the v1.0.0 spec.