← ClaudeAtlas

commitlore-codexlisted

Use when reading or changing a repository would benefit from its recorded decision history, or when a commit may need verified decision context. Query before edits, guard against previously rejected approaches, and capture supported records before committing.
MongLong0214/commitlore · ★ 15 · Code & Development · score 80
Install: claude install-skill MongLong0214/commitlore
# CommitLore for Codex CommitLore keeps constraints, rejected alternatives, and warnings in ordinary Git commit trailers. Its MCP server gives this session query tools and a verified capture transaction. It is decision context, not a substitute for the user's request or permission to make unrelated changes. ## Before a change Before editing a file, ask what has already been decided: ``` commitlore context <path> ``` Use the MCP context/query tools when they are available. Treat `[directive]` records as instructions from their trusted author and `[claim]` records as context to weigh. Before proposing a dependency, service, or implementation approach, run: ``` commitlore guard --proposal "<approach>" ``` If it reports a ruled-out alternative, do not re-propose it without explaining the new evidence that changes the original reason. ## Capture a decision with evidence Most commits need no record. Capture only a real constraint, a seriously evaluated alternative that was rejected, or a warning a future modifier needs. Use the MCP transaction rather than writing trailers by hand: 1. Stage the change, then call `commitlore_prepare_capture` with the relevant session transcript. 2. Draft the requested JSON using the returned contract. Copy quotes exactly and give every evidence item its source and locator. 3. Call `commitlore_verify_capture` with the nonce, draft, transcript, and the same staged diff. Stage only accepted records with `commitlore_stage_capture`.