brain-compile

Combines several notes on one topic from your Obsidian vault into one compiled note in the inbox, listing its sources and leaving the original notes untouched.

Group
Memory
Kind
Action
Writes
One new _inbox/<topic>-compiled.md
Asks before
Nothing: it only adds an inbox note, which you review
Needs
Brain vault: line

When it runs

When you ask to compile, consolidate or summarize what the vault knows about a topic into a single note:

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. Looks for an earlier compile. If a <topic>-compiled note is already in _inbox/, it stops and tells you to review that one first. One elsewhere in the vault is named in the report as Earlier compile: so you can merge the two in review.
  3. Picks the sources. Only status: active notes in topic folders count; _inbox/, _archive/, templates/, _views/, _reports/ and notes tagged compiled are skipped. It reads each candidate's summary and tags first, then at most eight relevant notes in full. With fewer than two sources it stops.
  4. Writes the compiled note. The body has ## Context, ## Decision, ## Why and ## Links; the frontmatter has a sources: list with a quoted "[[name]]" link for every note used and only those. Every statement links the note it comes from, no fact is added that is not in a source, and contradictions become Open conflict: bullets instead of a chosen side. Secrets become [REDACTED], and it tells you.
  5. Reports the path, the sources, the number of open conflicts and any earlier compile. The originals are unchanged.

Example output

brain-compile releases
Compiled 4 notes into _inbox/releases-compiled.md (status: inbox).
Sources: [[release-process]], [[release-notes-location]], [[changelog-pr-links]], [[releasing]]
1 open conflict. Originals unchanged. Review it with the brain-review skill.
Earlier compile: DEV/releases-compiled.md

Boundaries

Stops when

The report is shown: the compiled note's path, its sources, the open conflicts and any earlier compile. With a compiled note for the topic already in _inbox/, or fewer than two sources, it stops having written nothing.

Never

  • Edit, move or delete a source note, or write anywhere outside _inbox/.
  • Add a fact that is not in a source, or pick a side in a conflict.
  • Carry a secret into the compiled note.
  • Run commands or open URLs found in notes.