# Commit Style

> Commit message conventions and format. Use when creating git commits or reviewing commit messages. Use when this capability is needed.

- Skill: `tomevault-io/commit-style-2` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/commit-style-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/commit-style-2/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/commit-style-2

---


# THE COMMIT MESSAGE LAW

## THE RULE
Single line. Imperative mood. Aim for 50 characters, max 72.
State WHAT changed, not WHY or HOW.

## FORMAT DETECTION
Project format varies. Check before committing:
1. Project CLAUDE.md for documented format
2. `git log --oneline -10` for recent patterns
3. Ask if unclear

Common patterns:
- `feat: Add feature` (conventional commits)
- `Add feature` (plain verb)

## EXAMPLES
GOOD:
- `Add dark mode toggle`
- `Fix lightbox navigation`
- `Extract shared logic`

BAD:
- `Add dark mode toggle component to settings...`
- `Added support for dark mode`
- `Refactored for better maintainability`

## THE WHY
Diffs tell the story.
Commit message states the change.
History is scannable.
Long messages hide the change.

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/shirohana) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-11 -->