What problem does it solve? Commit messages often lose the reasoning behind a change, making it hard for teams to understand why a decision was made months later. This Skill standardizes commit messages with the Lore format so every commit records constraints, rejected alternatives, confidence, and test coverage alongside the code. ## Core Features & Use Cases - Structured Commit Format: Enforces a type(scope): subject convention with types like feat, fix, refactor, test, docs, chore, and perf. - Decision Trailers: Adds Lore trailers such as Constraint, Rejected, Confidence, Scope-risk, Reversibility, Directive, Tested, Not-tested, and Related to capture decision context. - Automated Validation: Integrates with auto check --lore for type prefix and sign-off checks, and auto lore validate for required trailer and value validation. - Use Case: When committing a JWT authentication change, generate a message that records the rejected session-store alternative, medium confidence, module-level scope risk, and the related SPEC-AUTH-001 ticket. ## Quick Start Ask the agent to write a Lore-format commit message for your staged changes, including the decision trailers and Autopus sign-off.