obsidian-brain

Identify changed code and dispatch reuse, quality, and efficiency reviewer agents in parallel; return the raw findings list.

Review changed code for reuse, quality, and efficiency, and produce a triaged list of findings (no edits). Use after writing code, for simpler code with fewer bugs and better performance.

Provides guidance on good software design principles, with trade-off calibration, examples, and common failure modes. Applies when making decisions while writing, designing, or refactoring code, or evaluating trivial code for clarity, maintainability, and common mistakes.

Reviews code with a team against established software design principles, and returns triaged findings (no edits). Use when evaluating code, or after writing or refactoring complex code, systems or technical designs: for code that is clearer, easier to maintain, and avoids common mistakes.

Shared setup for shaping sessions. Determines if an artefact exists or needs creating, creates it if needed, starts the transcript, reads the type taxonomy. Called by the parent router or by any sub-skill invoked directly.

Shape an artefact through structured Q&A. Routes to the right sub-skill: brainstorm (new/unclear artefacts), refine (open decisions), or discover (exploration-driven artefacts like People and Ideas).

Review changed code for reuse, quality, and efficiency, then fix any issues found.

Enforces vault workflow rules when working on artefacts in the Brain Obsidian vault. Triggers whenever the user asks to create, edit, refine, or reorganise content in the vault — wiki pages, logs, transcripts, or vault structure itself. Also triggers for vault maintenance tasks like refactoring, restructuring, or bulk updates. Use this skill any time work will result in files being created or modified in the vault, even if the user doesn't explicitly mention "vault" or "maintenance".

Use when an artefact is clear but has open decisions to work through. Convergent, decision-driven shaping for Designs, Plans, Tasks, Reports, Research, Presentations, Printables, Mockups.

Use when an artefact is new or a stub without enough information to start making specific decisions. Explores the idea through collaborative Q&A, writes content into the artefact, then hands off to refine.

Use for exploration-driven artefacts — People, Ideas, Cookies, Journal Entries, Thoughts. Open-ended Q&A to surface what's worth capturing. No decision table.

Structured evaluation using a swarm of small agents. The orchestrator assesses the target, designs a test plan mixing verifiable questions, trick questions, and navigation tasks, proposes it for user approval, then dispatches and synthesises scored results.

Quick quality check using a swarm of small agents. Each agent tries to accomplish a real task using the work product and reports where it got stuck. Gaps are identified, proposed to the user, and fixed. Use after completing a body of work, to tighten quality, or find what you missed.

Dispatch a swarm of small agents to test docs, implementations, or designs. Two modes: 'review' (quick comprehension check with fix-and-iterate) and 'evaluate' (structured evaluation with scored results and recommendations).