{"slug":"commit-message","title":"commit-message","summary":"Git commit message conventions: structure, formatting, scoping, body content, breaking changes, trailers.","platform":"Claude","tags":[],"authorName":"LLM Mart","authorSlug":"llm-mart","score":0,"source":"github","price":null,"verified":false,"createdAt":"2026-11-10T18:27:16.8917Z","repo":{"url":"https://github.com/xobotyi/cc-foundry","stars":23,"forks":2,"license":"MIT","updatedAt":"2026-11-10T17:16:40Z"},"bodyHtml":"<hr>\n<h2>name: commit-message\ndescription: &gt;-\nGit commit message conventions: structure, formatting, scoping, body content, breaking changes,\ntrailers.\nwhen_to_use: &gt;-\nInvoke whenever a commit message is touched at all — writing, reviewing, validating, amending, or\ncorrecting one the validator rejected. Also invoke on the symptoms: a body that walks the reader\nthrough the new code, a subject that sells the change, a message that records the test results of\nthe session. Covers the message text; splitting the work into units belongs to the commit skill.\nuser-invocable: false\ncompatibility: Uses Claude Code frontmatter beyond the Agent Skills spec (when_to_use, user-invocable)</h2>\n<h1>Commit Message Format</h1>\n\n<p>A commit message is a factual record of one change. It tells the reader why the change happened. The reader has the diff\nand the docs. The message adds only what the diff and the docs cannot show.</p>\n<h2>What Makes a Good Message</h2>\n\n<h2>Structure</h2>\n\n<h3>ASCII Symbols</h3>\n\n<h2>Subject Line</h2>\n<ul>\n<li>With a scope, for a monorepo: <code>[scope] &lt;verb&gt; &lt;description&gt;</code></li>\n<li>Without a scope, for a single-purpose repo: <code>&lt;verb&gt; &lt;description&gt;</code></li>\n</ul>\n\n<h3>Scope (Optional)</h3>\n\n<h2>Body</h2>\n\n<h3>Shape</h3>\n\n<h3>Record, Not Documentation</h3>\n\n<h3>Terse Register</h3>\n<p>The diff carries the <em>what</em>. The message carries the <em>why</em>. A body can use fragments, and it can drop articles where the\nmeaning stays clear. Identifiers, file paths, and error strings stay exact.</p>\n<p><strong>The tense carries the timeline.</strong> State the current behavior in the plain present tense, because the commit itself\nmarks the \"now\". The past tense belongs to the cause of the change, and to nothing else:\n<code>Empty input dereferenced nil. Returns empty token list instead.</code></p>\n<p><strong>Never include:</strong></p>\n<ul>\n<li>\"This commit does X\", \"This change...\". The diff says what.</li>\n<li>\"I\", \"we\". The commit speaks for itself.</li>\n<li>\"now\", \"currently\", \"previously\". The tense already carries the timeline.</li>\n<li>The old behavior as a contrast: \"X, where Y used to\", \"no longer does Y\", \"changed from Y to X\". The diff holds the\nprevious code. Name the old behavior only as the cause of a fix, or as the thing that a <code>BREAKING:</code> change removes.</li>\n<li>\"As requested by...\". Use a <code>Co-Authored-By:</code> trailer, or write nothing.</li>\n<li>The scope repeated: <code>[parser] update parser code</code> becomes <code>[parser] handle empty input</code>.</li>\n<li>Promotional adjectives without data: \"great\", \"amazing\", \"improved\", \"better\". Say what is better.</li>\n<li>Filler: \"just\", \"really\", \"basically\", \"actually\", \"simply\". Connective fluff: \"however\", \"furthermore\",\n\"additionally\".</li>\n<li>Session artifacts: test counts, lint status, typecheck status, build status, quality-gate status, CI results, and\nverification stories. Examples: \"55 of 55 tests passing\", \"all checks pass\", \"verified by building X\". These record\nyour session at commit time, not the change. A future reader cannot verify them, and the next commit makes them stale.\nSteps that a reader repeats are correct in the body. A log of the checks that you ran is not.</li>\n</ul>\n<h2>Breaking Changes</h2>\n\n<h2>Trailers (Footer Metadata)</h2>\n<p>Trailers are structured key-value pairs at the end of the commit message. They use the\n<a href=\"https://git-scm.com/docs/git-interpret-trailers\">git-trailer format</a>.</p>\n\n<h2>Amending Commits</h2>\n\n<h2>No AI Attribution</h2>\n\n\n","files":[{"path":"SKILL.md","sizeBytes":13925,"isText":true}],"reviewScore":null,"reviewSummary":null,"trust":{"provenance":"trusted-source-unreviewed","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow.","bodySource":null},"bodyLocked":false,"purchaseUrl":null,"sourceUrl":null,"report":{"provenance":"trusted-source-unreviewed","screen":{"ran":true,"outcome":"clean","suspicious":0,"notes":0,"hiddenCharacters":false},"virusScan":{"engine":"clamav","status":"clean","scannedAt":"2026-11-10T18:27:27.601829Z","sha256":"0961C94ACDAEB3EB9EE7C754123A6DD38129CC3A12C6CE584B2983E04C21DBC7","sizeBytes":5805},"review":null,"source":{"repositoryUrl":"https://github.com/xobotyi/cc-foundry","path":"plugins/git-commit/skills/commit-message","license":"MIT","commit":"278c16c0c371ac3ef36b12512ca558c7513ef13e","subtreeSha":"267CFB7C551EB6B49FFAE43D75F8E46B48D506BCA6B4E12BDA29721338E65614","lastSyncedAt":"2026-11-10T18:27:15.736835Z"},"reviewedAt":"2026-11-10T18:27:55.198506Z","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow."},"install":[{"target":"skills-cli","command":"npx skills add https://github.com/xobotyi/cc-foundry/tree/master/plugins/git-commit/skills/commit-message"},{"target":"claude-code","command":"claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install xobotyi-cc-foundry@llmmart"},{"target":"git","command":"git clone https://github.com/xobotyi/cc-foundry.git"}]}