← ClaudeAtlas

akashic-recordlisted

Generate and incrementally maintain a repo wiki (.akashic/wiki) with line-range source citations. Use when asked to generate or create a repo/project wiki, update or refresh the wiki, check wiki status, or when a repo already has .akashic/ and its architecture docs could answer the question. Triggers - /akashic-record, "repo wiki", "generate wiki", "update the wiki", "wiki status".
ARMeeru/akashic-record · ★ 0 · AI & Automation · score 63
Install: claude install-skill ARMeeru/akashic-record
# akashic-record Generates a repo-committed wiki under `.akashic/wiki/` — architecture pages with plain Mermaid diagrams and per-section line-range citations into source — and keeps it fresh by regenerating only pages whose underlying files changed. Format spec: `DESIGN.md` next to this file. ## Hard rules 1. **The script is the only authority** for hashes, diffs, staleness, and citation validity. Never compute or guess any of those yourself, and **never edit the `anchor`, `hash`, `files`, or `generated` fields of `catalog.json` by hand** — there is no exception. Immediately after you (re)generate a page, run `bless <id>` instead; that nulls its hash, which is the signal that the tool wrote the current text. `anchor` records a new hash only for pages whose hash is null or unchanged, and preserves the recorded hash of anything else (human edits stay protected across anchors). `goal`, `scope`, `title` and `parent` are yours to edit; the four fields above are the script's. 2. **Never overwrite a page the script reports as `edited`.** That is detected human work. Regenerate it only when the user explicitly asks, and then pass the current human text into the generation prompt as immutable context to preserve. 3. **Cite-or-omit**: every claim a reader would act on carries a `Sources:` citation; if you cannot cite it, do not write it. 4. Every mutating flow ends `verify` → fix until clean → `anchor`. Never leave the wiki un-anchored. ## The he