← ClaudeAtlas

docslisted

Browse the auto-generated `.br8n/docs/` tree distilled from your session notes — list and read the curated docs, map folders to files, and surface the most relevant ones for the user's question; pass `--rebuild` to force a fresh distill. Use when the user wants to read the project's living docs, find the doc covering a topic, or refresh the tree after new notes landed.
anthonysuherli/br8n · ★ 2 · Data & Documents · score 75
Install: claude install-skill anthonysuherli/br8n
# br8n — Docs (browse the living doc tree) br8n distills the per-KB session notes (see [`/br8n:notes`](../notes/SKILL.md) and [`../_shared/session-note.md`](../_shared/session-note.md)) into a curated documentation tree at `<project_path>/.br8n/docs/`. **Notes are the source; docs are the synthesis.** This skill reads that tree and presents it; `--rebuild` forces a refresh. The tree is git-ignored and regenerated — never hand-edit it; to change what it says, edit the notes or the note policy and re-distill. ## Step 0 — Resolve target `project` = git repo basename, `kb` = git branch, `project_path` = repo root (see [`../_shared/preamble-first.md`](../_shared/preamble-first.md)): ```bash basename "$(git rev-parse --show-toplevel)" # project git branch --show-current # kb git rev-parse --show-toplevel # project_path ``` No prior tap needed — the docs are plain files in the working tree. ## Step 1 — Read the tree The curated docs are markdown files on disk under `<project_path>/.br8n/docs/`. Read them with your **own** file tools — they're in the working tree, no MCP call needed: 1. `Glob` for `<project_path>/.br8n/docs/**/*.md` to enumerate the tree. 2. `Read` the files that matter (all of them if small; the relevant subset if large). 3. Present a concise **map** — folders → files — then surface the most relevant doc(s) for the user's query or current intent: > **Living docs** — `<project>` / `<kb>` > - `<folder>/` — `<file