# Commit Message

> Generates clear Git commit messages using Conventional Commits. Use when crafting a subject line and body for a change.

- Skill: `tomevault-io/commit-message-11` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/commit-message-11`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/commit-message-11/raw
- Safety review: pending
- 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-message-11

---


# Commit Message Guidelines

## When to Use
- You need a high-quality Git commit message.
- You want consistent Conventional Commits formatting.

## Procedure
1. Identify the primary change and select the Conventional Commit type.
2. Write the subject line in 50 characters or fewer.
3. Add a blank second line.
4. In the body, explain why the change was needed and the key details.
5. Prefer "Because there was an issue with ..., fix ..." over "Fix ...".

## Conventions
- Use the Conventional Commits format.
  - Prefixes: `feat:`, `fix:`, `docs:`, `style:`, `refactor:`, `test:`, `chore:`
  - Example: `feat: introduce Devise to provide authentication`

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

