commit

Format git commit messages with emoji conventional templates and enforce a 72-character title limit.

1|Updated Apr 17, 2023

Search Tags:#automation #git #template #commit #emoji #version-control #conventional

Ready to run

npx skills add https://github.com/mainliufeng/dotfiles --skill commit-mainliufeng

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces the embedded emoji conventional template for git commits, ensuring consistent commit messages across the repository.

Core Features & Use Cases

Embedded Template: Commit messages follow emoji type, summary, and bullet body
Title Length Rule: Keeps the title within 72 characters
Rationalization & Examples: Provides concrete examples and rationale

Quick Start

Use the commit template whenever a git commit is required in this repo. <emoji> <type>: <summary>

<bullet>

Example: ✨ feat: Add new authentication flow

Implement auth route
Update tests
Update docs

Frequently Asked Questions about commit

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

FAQPage Schema

How do I enforce consistent git commit message formatting across my repository?▼

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.

What is the emoji conventional commit template and why use it?▼

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.

How do I structure a commit message with emojis and a 72-character limit?▼

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.

Can I apply emoji commit templates to automated commits in my repository?▼

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.

What happens if my commit message exceeds the 72-character title limit?▼

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.

Does this template work with version control workflows beyond basic commits?▼

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.