# Commit Message > Generates commit messages from git diffs and user-provided change context. Use when user says "write commit message", "generate commit", or invokes "/commit-message". Auto-triggers when committing changes. - Skill: `bastienlimbour/commit-message` (Agent Skill) - Install (CLI): `npx skillmds@latest add bastienlimbour/commit-message` - Raw SKILL.md: https://api.skillmd.com/api/skills/bastienlimbour/commit-message/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: bastienlimbour (https://skillmd.com/u/bastienlimbour) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/bastienlimbour/commit-message --- # Commit Message Write a concise commit message. Follow the Conventional Commits format. No fluff. Why over what. ## Workflow ### 1. Choose the diff source If the user provides a raw `git diff` output, use it as the diff to analyze. Otherwise, run `git status` to see staged/unstaged files; detect no changes at all. Then: 1. If **Staged non-empty**: Analyze **only** `git diff --staged`. Do not include unstaged changes, even if they exist. 2. If **Staged empty**: Analyze `git diff` (unstaged changes). 3. If **Both empty**: Rely on the user's description; if none was provided, say there is nothing to commit and do not invent a message. ### 2. Gather the Change Context When the user provides a description, intent, scope, issue link, or other context in their message: - The selected diff is the source of truth for **what** changed. - User context clarifies **why**, scope, or nuances not visible in the diff. - Do not contradict the diff; if context and diff diverge, follow the diff and briefly note the mismatch. Infer from the selected diff and any plain descriptions of changes: 1. **What changed** — files, functions, logic affected by the changes 2. **Why it changed** — bug fix, new feature, refactor, performance, etc. 3. **Who/what triggered it** — issue number, user request, tech debt, etc. ### 3. Write the Commit Message Follow this structure: ``` ():