# Commit Message Crafter > Generate best-practice git commit messages (Conventional Commits) by inspecting changes, choosing type/scope, and producing concise, high-signal summaries in English. Use when this capability is needed. - Skill: `tomevault-io/commit-message-crafter` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/commit-message-crafter` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/commit-message-crafter/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-crafter --- # Commit Message Crafter Use this skill when the user wants help writing commit messages or asks for best commit messages. When the change set spans distinct concerns (features, fixes, docs, tests), prefer multiple focused commits instead of one large commit. ## Quick workflow 1) **Inspect context and split when needed** - Prefer `git status -sb` and `git diff` (or PR summary if provided). - Identify: what changed, why, and impact. - Detect breaking change risk and migrations. - Group changes by concern (e.g., fix vs test vs docs). If there is more than one clear concern, plan multiple commits. 1) **Use Conventional Commits only** - Always use Conventional Commits; do not ask about other styles. 1) **Craft the message(s)** - Subject is **imperative**, **short**, and **specific**. - **Avoid**: “WIP”, “misc”, “stuff”, “update”, or long diffs in subject. - Keep ASCII unless the repo clearly uses non-ASCII. - Always write commit messages in English. - If multiple commits are planned, propose a commit plan (ordering + scope) and produce a message for each. 1) **Optional body and footer** - Use a body when the change is non-trivial or has tradeoffs. - Wrap body at ~72 chars, use short bullets if helpful. - Add `BREAKING CHANGE:` footer when applicable. - Add issue refs if provided by the user. ## Conventional Commits template ```txt ():