lore-commit

Writes structured commit messages with Lore decision-record trailers.

111|73|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/autopus-ai/autopus-adk --skill lore-commit-autopus-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lore-commit
Source: https://github.com/autopus-ai/autopus-adk/tree/main/.omp/skills/lore-commit
Command: npx skills add https://github.com/autopus-ai/autopus-adk --skill lore-commit-autopus-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about lore-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a commit message that records design decisions?▼

Use the Lore commit format: start with a type(scope): subject line, add a body explaining background and intent, then append trailers like Constraint, Rejected, Confidence, Scope-risk, and Tested. Finish with the Autopus sign-off trailer.

What commit types does the Lore format support?▼

The Lore format supports seven type prefixes: feat for new features, fix for bug fixes, refactor for code improvements, test for test changes, docs for documentation, chore for build and config changes, and perf for performance improvements.

How do I validate Lore commit messages automatically?▼

Run auto check --lore to verify the type prefix and Autopus sign-off, and run auto lore validate to check that required trailers are present and that Confidence, Scope-risk, and Reversibility contain valid values.

What values are allowed for Confidence, Scope-risk, and Reversibility trailers?▼

Confidence accepts low, medium, or high. Scope-risk accepts local, module, or system. Reversibility accepts trivial, moderate, or difficult. The auto lore validate command rejects values outside these sets.

Are Why, Decision, and Alternatives trailers still standard in Lore commits?▼

No. The current Lore protocol centers on the Constraint trailer, and the older Why, Decision, and Alternatives examples are no longer the standard. New commits should use the Constraint-centered trailer set.