commit-message

Enforce atomic, imperative commit messages with 52-57 character summaries.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/doolin/dave-skills --skill commit-message-doolin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/doolin/dave-skills/tree/main/skills/commit-message
Command: npx skills add https://github.com/doolin/dave-skills --skill commit-message-doolin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit messages shape project history and review efficiency. They are often inconsistently written, making it hard to understand why changes were made and how they relate to other work.

Core Features & Use Cases

  • Atomic commits that encapsulate a single logical change.
  • Imperative, concise summaries in the 52-57 character range to describe the change at a glance.
  • Templates by change type for New feature, Bug fix, Refactor, Cleanup, Documentation to standardize messages.
  • Guidance on private vs public history to support draft commits and clean release histories.

Quick Start

Draft a concise, imperative commit message that clearly describes the change.

Frequently Asked Questions about commit-message

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

FAQPage Schema
How do I write effective git commit messages for better code history?

Effective git commit messages use imperative mood and concise summaries of 52-57 characters to describe the change at a glance. This enforces consistent, descriptive project history and improves review efficiency across software projects.

What is an atomic commit in version control?

An atomic commit encapsulates a single logical change within your version control history. This practice keeps code changes focused, making it easier to understand why modifications were made and how they relate to other work.

How do I manage private draft commits versus a clean public release history?

You manage private versus public history by using draft commits during active development and cleaning them up for release. This approach supports a consistent, descriptive public history while allowing flexible private work.

Do I need a specific git workflow to use structured commit templates?

No specific git workflow is required. The templates apply when writing code changes, reviewing history, and preparing PRs across any software project, ensuring adherence to best practices like imperative summaries and atomic commits.

What is the best way to format git commit summary lines?

The best way to format git commit summary lines is using the imperative mood within a 52-57 character limit. This concise format describes the change at a glance and maintains clarity across version control history.