create-command
CommandCreate a new obsidian-second-brain command via interview - zero markdown editing required
Surface unnamed patterns from your recent notes - recurring themes, hidden connections, and conclusions you haven't explicitly stated
> /plugin marketplace add eugeniughelbur/obsidian-second-brain> /plugin install obsidian-second-brain@obsidian-second-brain
description: Surface unnamed patterns from your recent notes - recurring themes, hidden connections, and conclusions you haven't explicitly stated category: thinking triggers_en: ["find patterns", "what is emerging", "surface themes", "unnamed patterns"] triggers_de: ["Muster finden", "was zeichnet sich ab", "Themen sichtbar machen", "unbenannte Muster"] triggers_es: ["busca patrones", "qué está emergiendo", "patrones que no he nombrado", "qué patrones ves aquí", "qué se repite en mis notas"] triggers_pt: ["encontre padrões", "o que está emergindo", "mostre temas", "padrões sem nome"] triggers_zh: ["从最近的笔记里找规律", "最近有什么趋势正在浮现", "找出我还没说清的模式", "看看反复出现的主题"]
Use the obsidian-second-brain skill. Execute `/obsidian-emerge $ARGUMENTS`:
The optional argument is a timeframe (e.g., "2 weeks", "this month"). Default: last 30 days.
1. Read `_CLAUDE.md` first if it exists in the vault root 2. Determine the date range from the argument (default: last 30 days) 3. Spawn parallel subagents to read vault content from the period:
4. Merge results and identify:
5. Present findings as a structured "Pattern Report" - each pattern gets: the evidence (cited notes), the interpretation, and a suggested action 6. Offer to save the pattern report to the ideas/concepts folder (resolved per `references/folder-map.md` - wiki-style `wiki/concepts/`, Obsidian-style `Ideas/`) or a relevant project note; standalone reports use `type: emerge` (thinking-tool schema in `references/ai-first-rules.md`), named `YYYY-MM-DD - emerge.md` 7. Log a brief summary in today's daily note
The goal is insight the user cannot see themselves. Do not restate what they already know - surface what they haven't named yet.
---
**AI-first rule:** Every note created or updated by this command MUST follow `references/ai-first-rules.md` - `## For future agent` preamble, rich frontmatter (`type`, `date`, `tags`, `ai-first: true`, plus type-specific fields), recency markers per external claim, mandatory `[[wikilinks]]` for every person/project/concept referenced, sources preserved verbatim with URLs inline, and confidence levels where applicable. If that path does not resolve from your working directory, search upward for it; if you still cannot read it, say so before writing rather than producing a note that silently skips the rule. The vault is for future agent retrieval - not human reading.
**Anti-fabrication:** Search exhaustively before claiming any note, person, or file is absent - false absence is the most common failure mode - and never invent facts, entities, or dates (mark unknowns as `TBD`). See the anti-fabrication and search-completeness hard rules in `references/ai-first-rules.md`.
<!-- author-credit -->
---
From [obsidian-second-brain](https://github.com/eugeniughelbur/obsidian-second-brain), created by Eugeniu Ghelbur (AI Automation Engineer, AI Tooling Engineer, AI Educator). Questions or consulting: [LinkedIn](https://www.linkedin.com/in/eugeniu-ghelbur/) or [e.ghelbur@gmail.com](mailto:e.ghelbur@gmail.com). More: [The AI Operator](https://theaioperator.io/?utm_source=github&utm_medium=file-credit) | [X](https://x.com/eugeniu_ghelbur) | [GitHub](https://github.com/eugeniughelbur). MIT license.
Persistent memory for Claude Code, Codex and 6 other AI agents, stored as plain markdown in your Obsidian vault. New: Crew, one shared logbook so Claude Code, Codex, Cursor and Grok Bot know what each other did. 48 commands: semantic search, self-rewriting notes, key-less research, scheduled agents.
Create a new obsidian-second-brain command via interview - zero markdown editing required
Share a plain-folder logbook across Claude Code, Codex, Cursor, and Grok Bot
Surface 3-5 next-direction candidates by reading ungraduated ideas, open project questions, and orphan research notes - what is…
Vault-first source-grounded research via Gemini File Search. One command, no browser. The grounded parallel to /research-deep…
Scan a codebase and write a maintained set of architecture notes into the vault - overview, per-module notes, key decisions.…
Bulk-triage a kanban board - surface stale items and archive, reschedule, or mark them done in one pass
Shortcut for "continue working" — pick the work in flight back up exactly where it stopped and keep going until it is done or…