# Lore Commit > Draft git commit messages that follow the Lore protocol: intent-first subject, optional narrative body, and git-native trailers such as Constraint, Rejected, Confidence, Scope-risk, Directive, Tested, and Not-tested. Use when a repo or user asks for Lore commits, structured decision-record commit messages, or commit trailers beyond a normal Conventional Commit. - Skill: `fengbuming/lore-commit` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add fengbuming/lore-commit` - Raw SKILL.md: https://api.skillmd.com/api/skills/fengbuming/lore-commit/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: fengbuming (https://skillmd.com/u/fengbuming) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/fengbuming/lore-commit --- # Lore Commit Use this skill to write a commit message, not to run `git commit`. ## Workflow 1. Inspect the staged or described change. 2. Identify the change intent, important constraints, rejected alternatives, verification performed, and any real verification gaps. 3. Write an intent-first subject line that explains why the change was made, not what files changed. 4. Add a short body only when the why is not obvious from the subject alone. 5. Add only the trailers that add value. Omit any trailer you cannot support with evidence. ## Format ```text Constraint: Rejected: | Confidence: Scope-risk: Reversibility: Directive: Tested: Not-tested: Related: ``` ## Rules - Subject explains why, not the file edit. - Use git-native `Key: value` trailers after a blank line. - Multiple `Constraint:` or `Rejected:` lines are allowed when needed. - Keep trailers factual. If a fact is unknown, omit it instead of guessing. - Include `Not-tested:` whenever there is a real verification gap. - Do not include filler such as "This commit does...", AI attribution, or file-by-file narration. - If the repo also requires another convention, satisfy the repo requirement first. If requirements conflict, say so explicitly. ## Output - Return only the commit message in a fenced `text` block unless the user asked for explanation. - Do not stage files, run `git commit`, or amend history. ## Example ```text Prevent retry storms after scanner reconnect The reconnect path was replaying queued jobs before the device health check finished, which caused duplicate submissions under brief network flaps. Constraint: Upstream scanner SDK reports reconnect before transport is stable Rejected: Add fixed 5s delay | hides race and slows healthy reconnects Confidence: high Scope-risk: narrow Directive: Do not move queue replay earlier without re-testing transient reconnect behavior Tested: Manual reconnect with queued jobs Not-tested: Long-running reconnect soak test ```