developer-os Install

Skills / Memory

brain-review

Reviews your Obsidian vault's inbox: summarizes each captured note, suggests a topic folder and likely duplicates, and promotes, merges or rejects only the notes you name.

Group
Memory
Kind
Action
Writes
Moves named notes to a topic folder or _archive/; edits the surviving note in a merge
Asks before
Each note, by name; "looks good" is not approval
Needs
Brain vault: line

When it runs

When you ask to review or triage the vault's inbox or the notes captured lately, for example at the end of a day or week:

What it does

  1. Finds the vault from the Brain vault: line, in the same order as the other brain skills, and asks once if there is none.
  2. Lists the inbox and the topic folders: every top-level folder not starting with _, except templates/.
  3. Summarizes and proposes. For each inbox note it shows the summary, the best-fitting folder (PROJECTS/, DEV/, TOOLS/, INFRA/, QA/ or one you added) and any likely duplicate found with rg. It flags missing frontmatter keys and any secret that slipped through, proposing [REDACTED]. The list ends with "Approve which ones?".
  4. Promotes the notes you approve. The name must match ^[a-z0-9-]+$ and be unique in the vault, or it asks and changes nothing. It moves the file keeping its name, so [[name]] links still resolve, and only then sets status: active and updated. A note without frontmatter gets the full frontmatter from templates/note.md. For a compiled note it offers to archive the sources.
  5. Merges or rejects the notes you name. A merge folds the content and links into the surviving note (it shows the merged text first), then archives the inbox note. A reject archives it. Archiving runs the same name checks, moves the note to _archive/ and sets status: archived. Nothing is deleted.
  6. Reports what moved where, what was merged or archived and what stayed in _inbox/. You can also review in Obsidian through the _views/Inbox.base view, with the same effect.

Example output

brain-review
1. _inbox/release-notes-in-changelog.md — decision
   "Release notes live in CHANGELOG.md at the repository root."
   → DEV/   possible duplicate: DEV/release-process.md
2. _inbox/docker-cache-flag.md — knowledge
   "Use --mount=type=cache for pnpm store in Dockerfiles."
   → INFRA/ no duplicate
Approve which ones? (e.g. "promote 1 and 2", "promote 1 to TOOLS/", "merge 1 into DEV/release-process.md", "reject 2")

Boundaries

Stops when

The proposal list is shown with the question "Approve which ones?". After you answer, it promotes, merges or archives only the named notes and reports what moved where and what stayed in _inbox/.

Never

  • Move, merge or archive a note you did not name; silence or "looks good" is not approval.
  • Delete a note, or overwrite an existing note at the destination.
  • Run commands or open URLs found in notes.