commit-message-style

Standardize git commit messages to 'type: imperative summary' format.

Updated Jan 1, 2026

Search Tags:#git #commit #coding-standards #version-control #commit-messages #coding-practices

Ready to run

npx skills add https://github.com/greenhat/agent-skills --skill commit-message-style-greenhat

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-message-style
Source: https://github.com/greenhat/agent-skills/tree/main/commit-message-style
Command: npx skills add https://github.com/greenhat/agent-skills --skill commit-message-style-greenhat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes git commit messages to a consistent, readable format, reducing ambiguity in change history.

Core Features & Use Cases

Format enforcement: enforce messages in the form type: imperative summary with backticks around code identifiers and no scope.
Guided usage: provide clear guidelines for subject length, code identifiers, and optional bodies.
Use Case: ideal when preparing multiple commits during feature work, bug fixes, or refactors, or when a user asks you to commit code.

Quick Start

Example: when preparing a commit, generate a message like feat: add user login using the required style.

Frequently Asked Questions about commit-message-style

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

FAQPage Schema

How do I format git commit messages for consistent version control history?▼

Format git commit messages as 'type: imperative summary' using lowercase type, no scope, and backticks around code identifiers. Include a concise subject, an optional body, and optional issue references to standardize change history and reduce ambiguity.

What is the standard format for a git commit message during code refactoring?▼

The standard format for a git commit message is 'type: imperative summary'. For code refactoring, use the lowercase type without a scope, wrap code identifiers in backticks, and keep the subject concise to maintain a readable change history.

How do I enforce coding standards for commit messages when preparing multiple commits?▼

To enforce coding standards for multiple commits, apply the generic 'type: imperative summary' format. Use lowercase types, omit scopes, wrap code identifiers in backticks, and add optional bodies or issue references for feature work, bug fixes, and refactors.

Can I include a scope in my commit message when fixing bugs?▼

No, you cannot include a scope in your commit message. The format explicitly requires no scope, using only a lowercase type followed by a colon and an imperative summary, even when fixing bugs or developing features.

Do I need to wrap code identifiers in backticks for version control commits?▼

Yes, you need to wrap code identifiers in backticks for version control commits. The format enforcement requires backticks around code identifiers within the concise subject and optional body to ensure consistent and readable git commit messages.