| name | csm |
| description | Retrieve and verify repository-owned semantic memory in a Git repository that has already adopted Codebase Semantic Memory. Use before changing code, when scope changes, and before claiming completion. |
Codebase Semantic Memory
This skill is available only because the current Git root contains csm.toml.
CSM and its managed tools remain authoritative; do not read .csm/ directly or
reproduce their ordering and checks.
Before editing, retrieve the relevant decisions, patterns, corrected failures,
and due work:
"${CSM_BIN:-csm}" context --task "<goal>" --path <expected-path>
The Prime extension injects this automatically when auto-context is enabled. If
a CSM AUTO-CONTEXT message already covers the current goal, do not duplicate
it unless scope or expected paths change.
Before claiming completion, run the repository proof and every enabled semantic
check:
"${CSM_BIN:-csm}" check --task "<completed work>" --base HEAD
A nonzero exit means the semantic contract is not satisfied. Report it; never
translate partial output, a failed provider, or a missing tool into success.
Use "${CSM_BIN:-csm}" doctor --json to diagnose installation state. Access an upstream tool
only through the managed proxy, such as "${CSM_BIN:-csm}" wtw explain ... or
"${CSM_BIN:-csm}" nya recall ..., so the Rust core keeps version and storage routing.
Never run csm init, csm adopt, or csm sync unless the user explicitly asks
for that administrative repository change. Never create semantic records merely
from conversation; recording a decision, pattern, scar, or due work remains an
explicit action through its owning tool.
