obsidian-kb

Audit your project's markdown docs against the actual code - flag stale claims with file:line evidence

Open the project's Obsidian vault and show the knowledge graph view

Alias for /kb-offboard - write a session handoff note to the project's Obsidian knowledge base

Initialize the project knowledge base - scaffolds a vault (if missing) and populates it with rich docs + stale-doc audit via parallel subagents

Write a session handoff note to the project's Obsidian knowledge base

Read the latest session handoff from the project's Obsidian knowledge base to get up to speed

Scaffold an empty Obsidian knowledge base vault for the current project (no codebase analysis - for that, use /kb-init)

Refresh the project's Obsidian knowledge base notes to reflect recent code changes

Audit the existing markdown documentation in the current project against the actual code. Flags stale claims with file:line evidence, categorizes each doc (current / partially stale / stale / aspirational), produces a single "Documentation Audit" note in the project's Obsidian knowledge base. Re-runnable at any time - use for quarterly doc refreshes or before a major rewrite. Use when the user asks to "audit our docs", "check for stale READMEs", "find outdated documentation", or types /kb-audit. Independent of kb-init's full populate flow.

Open the project's Obsidian vault in Obsidian and switch to the graph view, showing the knowledge base as a visual network of notes and their wiki-link relationships. Use when the user asks to "see the graph", "visualize the vault", "show me how notes connect", "open the graph view", or types /kb-graph. Also useful after kb-init to show off the newly rich vault.

Initialize the project knowledge base. If no vault exists, scaffolds one (via kb-scaffold) first. Then analyzes the codebase with parallel subagents and populates the vault with rich, structured documentation - mining existing markdown docs for insights but verifying every concrete claim against current code, so stale documentation doesn't pollute the vault. Produces curated notes plus a "Documentation Audit" report flagging outdated project docs. Use when the user asks to "initialize a knowledge base", "document this project", "populate the vault", "set up project memory", or types /kb-init. Always ask for confirmation before dispatching subagents - this uses meaningful compute and takes a few minutes.

Write a session handoff note to the project's Obsidian knowledge base so the next session can pick up seamlessly. Use when wrapping up a session, when the user says they're "done", "wrapping up", "that's it for today", or types /kb-offboard (even in environments without native slash command support - treat that as intent to trigger this skill). The handoff is adaptive - proportional to what actually happened in the session.

Brief the agent on what happened last session by reading the latest handoff note and project overview from an Obsidian knowledge base. Use when starting work on a project that has a knowledge vault, when the user asks to "catch up", "see what was done last time", "continue previous work", or types /kb-onboard (even in environments without native slash command support - treat that as intent to trigger this skill). Read-only - never modifies the vault.

Scaffold an empty Obsidian knowledge base vault for the current project - creates the folder structure and placeholder notes, but does NOT analyze the codebase or populate with content (for that, use kb-init). Use when the user asks to "just scaffold a vault", "create empty vault structure", "set up a bare vault", or types /kb-scaffold. Most users should use /kb-init instead for the full initialization flow. Always ask for confirmation before creating or deleting anything.

Refresh the project's Obsidian knowledge base notes to reflect recent code changes. Reviews git activity and session context, surgically edits stale KB notes with file:line evidence, and flags new concepts as candidates for user-approved notes (never silently creates them). Run after a significant refactor, before /kb-offboard at session end, or any time you notice the KB drifting from the code. Triggered by /kb-update or when the user asks to "refresh the KB", "update the knowledge base", "sync the vault with the code". Distinct from /kb-audit - this maintains the vault's own notes; /kb-audit checks the project's user-owned markdown.

Awareness skill for the obsidian-kb plugin. Nudges agents to suggest kb-init, kb-scaffold, kb-audit, kb-update, kb-onboard, kb-offboard, and kb-graph at the right moments - session start, session end, vault initialization, doc freshness checks, post-refactor KB refresh, visualization. Use when the user mentions session handoffs, project knowledge bases, onboarding, wrapping up, continuing previous work, initializing a vault, auditing stale docs, refreshing the KB after code changes, populating or enriching docs, visualizing the vault graph, or types any /kb-* command.