anthonysuherli

capture

Save the current workspace context to the br8n session KB as a snapshot — branch, open/cursor files, git diff stat, and a one-line hypothesis of what you're doing — AND sweep every other live Claude Code session, snapshotting each one's repo+branch in the background. Use when the user is about to switch away, says "save my context", "remember where I am", or wants to checkpoint intent before an interruption.

Data & Documents Listed

docs

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.

journal

Your cross-project personal journal — write an entry any time (insight, reflection, reference, decision) and search it back by meaning. Distinct from session notes (which are per repo+branch, written at session end); the journal is global and on-demand. Use when the user wants to jot a durable thought, "journal this", "note to self", or recall past entries ("what did I conclude about X", "search my journal").

notes

Dictate what kind of session notes br8n takes for this repo+branch — show the current note policy (section template + steer), edit it inline with free-text guidance, or launch a guided wizard to co-design it. Use when the user wants to control what end-of-session notes capture ("focus on architecture", "skip dep bumps"), review the policy, or set it up from scratch with `--wizard`.

pickup

Pick up where you left off — replay the resume card for the current repo+branch, or open a cross-repo selector over every repo you've captured to and resume any of them. Use when the user returns to work, asks "where was I", "what was I doing", or wants to jump back into a different repo than the one they're in.

schema

Design or reshape this repo+branch's knowledge-graph schema (its ontology) — the one human-in-the-loop seam of the self-maintaining KB. Use when the user wants to set up, review, or re-design the KG schema, when a drift offer was surfaced ("your graph has drifted… reshape it?"), or proactively to check whether the ontology still fits what's been collected. Calls br8n_schema_drift to decide cold-start vs drift, then runs the guided wizard.

timeline

Read back your append-only activity timeline for this repo+branch — a chronological log of session notes, context captures, and journal entries. Shows recent activity (last few days) by default, with the past-week view and the full all-time scroll alongside. Pass `--rebuild` to force a fresh rollup now. Use when the user asks "what have I been doing", wants a chronological work log, a daily/weekly recap, or to scroll their activity history.

embeddings

Inspect or switch how br8n embeds text for semantic search — remote (API key) or local (keyless, on-device ONNX). Use when the user asks why search returns nothing, wants search to work without an API key, wants to stop paying for embeddings, or asks which embedding model br8n is using.

Data & Documents Listed

activity

Query your cross-repo ACTIVITY knowledge graph — what you've been working on across all repos (repos touched, branches, files, work sessions, and the tasks behind them). Use when the user asks "what was I working on", "what have I touched lately", "what's connected to <file/repo>", or wants a cross-repo rollup rather than a single repo+branch resume.

Data & Documents Listed

explore

Force the br8n gap-fill pipeline — plan → web search → crawl → extract → merge — to seed or deepen the repo+branch KB from the web, then rebuild the synopsis. Use when /br8n:pickup returns coverage='gap', when starting a KB from scratch, or when the user explicitly wants fresh online research persisted into the session KB.

search

Ground a question in the br8n session KB, fill the gap from the web if needed, then answer — the ground → grow → answer front door. Use by default when the user asks a question against what this repo+branch session knows; reach for /br8n:pickup or /br8n:explore directly only when you want exactly one step.