commit-guidelines

Apply the Seven Rules of a Great Git Commit Message to compose commit messages, PR titles, and reviews.

Updated Aug 23, 2026

Search Tags:#git #documentation #commit #conventions #best-practices #code-review #git-commit

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide provides a structured approach to writing clear, consistent Git commit messages to improve history readability and code-review efficiency.

Core Features & Use Cases

Standardizes subject lines, length limits, and body formatting.
Guides usage in commits, PR titles, and reviews to maintain consistency.
Provides actionable examples and best-practice rules for everyday workflows.

Quick Start

Follow the Seven Rules when composing a commit message to ensure clarity and consistency.

Frequently Asked Questions about commit-guidelines

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

FAQPage Schema

What are the Seven Rules of a great Git commit message?▼

The Seven Rules of a great Git commit message standardize formatting by enforcing subject line length, capitalization, punctuation, and body structure to improve history readability and code review efficiency.

How do I format a Git commit subject line for better code reviews?▼

To format a Git commit subject line for better code reviews, apply standard guidelines that enforce proper capitalization, omit trailing punctuation, and limit length, ensuring clarity and consistency across software projects.

Can I use formal commit message guidelines for PR titles?▼

Yes, you can use formal commit message guidelines for PR titles. Applying these conventions to PR titles and code reviews maintains consistency and improves history readability across your software projects.

What is the best way to structure a Git commit body?▼

The best way to structure a Git commit body is to follow formal commit message guidelines, which provide actionable rules for body formatting that separate it clearly from the subject line and explain the changes.

Why does my Git commit history lack consistency?▼

Your Git commit history lacks consistency because messages are not following formal commit guidelines, leading to varied subject lengths, improper capitalization, and unstructured bodies that reduce code review efficiency.