commit

Enforce consistent git commit formatting using an emoji conventional template that requires a type emoji, concise summary, and structured bullet body. This Skill applies the template to all commits—manual and automated—ensuring messages follow a standardized format with titles limited to 72 characters.

The emoji conventional commit template combines a type emoji, summary, and bullet-point body to create scannable, searchable commit histories. It standardizes how changes are described, making version control logs easier to navigate and automation simpler to parse.

Start with an emoji and type (e.g., ✨ feat:), follow with a concise summary under 72 characters, then add a blank line and bullet-point details. This Skill enforces that structure automatically, ensuring every commit—whether manual or auto-generated—conforms to the template.

Yes. This Skill enforces the emoji conventional template across all commit types, including auto-commits and programmatic commits. It rewrites commit messages to meet the format requirements regardless of how the commit is triggered.

The Skill enforces the 72-character title constraint, preventing commits that violate it. Titles that exceed this limit are rejected, forcing you to condense the summary and move details into the structured bullet body.

Yes. The emoji conventional template integrates with standard git workflows, including manual commits, automation hooks, and CI/CD auto-commits. It ensures message consistency across all repository commit sources without workflow-specific setup.