← ClaudeAtlas

wiki-foldlisted

Roll up a range of the wiki's log into one fold page: extractive, bounded, and the same every time for the same entries; previewed first, applied as one operation on request. Use for fold the log, run a fold, log rollup, roll up log entries, what happened in the wiki lately, commit the fold. Never changes the entries or the pages they name.
nathanaday/atlas-obsidian · ★ 0 · Code & Development · score 72
Install: claude install-skill nathanaday/atlas-obsidian
# Fold the log `wiki/log.md` gets one entry per operation, so it grows without end. A fold is a page that rolls up a range of entries: what changed, which pages, and the themes across them, each line traced to its entry. It adds a page and changes nothing else. Never fold a fold, and never fold unasked. Tools: `status`, `plan`, `apply`. Reads [fold-template.md](references/fold-template.md) and [operations.md](../wiki/references/operations.md). ## Select a bounded range Use batch exponent `k` with size `2^k`; default to `k=4`. An explicit entry range may override it. If fewer entries exist than requested, report the shortfall and stop rather than folding a partial batch. Read the selected log entries completely. Read referenced child pages only when the log lacks enough context: target 0-10 reads, hard ceiling 15. A missing page stays an explicit `page_missing` record. Derive the structural id only from inputs: ```text fold-k{K}-from-{EARLIEST-DATE}-to-{LATEST-DATE}-n{COUNT} ``` If `wiki/folds/{FOLD_ID}.md` already exists, return a no-op. Replacing it needs an explicit request and a `replace` write the user reviews. ## Draft extractively Follow [fold-template.md](references/fold-template.md). Every child log entry has one deterministic `child_key` in frontmatter and exactly one matching row in the Child Entries table. Do not deduplicate children by page; the final Child Pages list may be deduplicated. Every outcome names its source entry. Every number is verifiable