commit

Generate conventional Git commit messages with subject and body rules.

102|4|Updated Apr 15, 2009

Search Tags:#git #commit #imperative-mood #body #git-commit #issues-prs #subject-line

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured guideline to write clear, conventional Git commit messages, improving traceability and collaboration across development teams.

Core Features & Use Cases

Enforces a concise subject line that starts with a capitalized imperative verb
Supports an optional body that explains what and why, wrapped to 72 chars
Allows referencing issues/PRs in the commit message
Provides examples illustrating compliant messages for common scenarios

Quick Start

Generate a concise, conventional Git commit message that follows subject/body rules and references related issues when applicable.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I write a conventional Git commit message with an imperative subject line?▼

A conventional Git commit message uses a concise subject line starting with a capitalized imperative verb. Enforce subject line capitalization and maximum length, separate the subject and body with a blank line, and use an optional body to explain what and why.

What is the maximum length for a Git commit subject line?▼

The maximum length for a Git commit subject line is enforced to keep messages concise. A capitalized imperative verb begins the subject, which is followed by a blank line before the optional body wraps at 72 characters to explain what and why.

How do I format a Git commit body for multiple changes?▼

To format a Git commit body for multiple changes, use bullet points to detail each modification. The body is separated from the subject by a blank line, wrapped to 72 characters, and explains what changed and why the changes were made.

How do I reference issues or PRs in a Git commit message?▼

To reference issues or PRs in a Git commit message, include the references within the message structure. The commit message supports referencing issues and PRs when relevant, alongside a capitalized imperative subject line and an optional body explaining what and why.

Do I need a specific Git workflow to generate conventional commit messages?▼

You do not need a specific Git workflow to generate conventional commit messages. The guidelines apply to software development workflows to generate or validate subject and body lines for single commits or grouped changes without requiring special dependencies.

Why use imperative mood in Git commit subject lines?▼

Imperative mood in Git commit subject lines provides clear, direct instructions about what the commit does. Enforcing a capitalized imperative verb ensures consistency, improving traceability and collaboration across software development teams.