grimoire-commit

To generate conventional commit messages from staged git changes, inspect the git diff and active grimoire context. This produces auditable messages with Change trailers and optional Scenarios or Decisions metadata, requiring explicit approval before committing.

Grimoire context works by reading configuration from .grimoire/config.yaml and the active change manifest to tailor commit structure and trailers. It combines staged and unstaged git diffs with this context to craft meaningful, auditable messages.

Yes, you can include Scenarios and Decisions metadata in conventional commits. The process generates commit messages with Change trailers and optional Grimoire metadata for Scenarios and Decisions to maintain an actionable audit trail.

The best way to keep an auditable git history is to generate contextual commit messages from staged changes and grimoire context. This ensures commits require explicit approval, never auto-commit, and include Change trailers for an actionable audit trail.

You need to configure .grimoire/config.yaml to define the commit_style and have an active change manifest. This configuration tailors the commit structure and trailers used when generating messages from your staged git changes.

No, this git commit workflow never auto-commits changes. It guides users through gathering context, validating changes, and presenting a ready-to-commit message that requires explicit approval before applying.