← ClaudeAtlas

atlas-recollectionlisted

Use when finishing a change in a repo that has an Atlas — before ending the session or opening a PR, to keep the vault's zone cards, stamps, and ledger entries in sync with the code just changed.
muslewski/status-herald · ★ 4 · AI & Automation · score 70
Install: claude install-skill muslewski/status-herald
# Recollection — maintain the Atlas on finish Recollection happens as part of finishing the change, not as a separate pass. Run this checklist before ending the session: - [ ] **Update touched zone cards.** Any zone card (`map/zones/<slug>.md`) whose `owns`/`depends`/`invariants` claims changed because of this change — edit it now, not later. - [ ] **Re-stamp exactly the zones you reviewed.** `atlas stamp <slug...>` — name only the zones whose owned code you actually changed and re-read against the card. Never a blanket re-stamp; there is no "all zones" shortcut, by design. Order matters: commit the code + card edits first, then stamp — `verifiedAt` anchors to the committed HEAD, so stamping before the commit leaves the zone stale. - [ ] **Decision record for any non-obvious why.** If the change involved a choice a future reader would ask "why did we do it this way," add a `map/decisions/NNNN-slug.md`. Obvious mechanical changes don't need one. - [ ] **Tech-debt note for every deferral.** Anything deliberately left undone gets a `tech-debt/` note (`type: debt`, `severity`, `effort`) — not a TODO comment, not a mention in a commit message only. - [ ] **Rebuild and check.** `atlas check` — regenerates `map/index.md` and verifies zone claims and the ledger (add `--strict` in CI to also fail on staleness). Commit the regenerated index together with the code change, in the same commit — never as a separate follow-up. - [ ] **Supersede, don't edit; tom