ClaudeCode & Obsidian: Teaser

I can write a fuller post on this later, but here's a sneak peek at how things can be, when you let ClaudeCode be "a local delegate" to your Vault.


Here's it processing my Inbox for me (some snippets or drafts that I added):


> /process

⏺ Update Todos
  ⎿  ☐ Check for new items in 00-Inbox/ to process      
     ☐ Analyze and process each unprocessed item
     ☐ Create refined documents in appropriate locations
     ☐ Update relevant MOCs and strategic documents
     ☐ Rename processed items with PROCESSED prefix
     ☐ Generate summary report of changes

⏺ List(00-Inbox)
  ⎿  Listed 16 paths (ctrl+r to expand)

⏺ Update Todos
  ⎿  ☒ Check for new items in 00-Inbox/ to process      
     ☐ Analyze and process each unprocessed item
     ☐ Create refined documents in appropriate locations
     ☐ Update relevant MOCs and strategic documents
     ☐ Rename processed items with PROCESSED prefix
     ☐ Generate summary report of changes

And here's it cataloguing for me all the custom commands' it's added:


> A meta question for you: Is there a way to list out the set of custom commands that have been defined?

⏺ Yes! There are several ways to access the custom commands:

  Quick Reference

  The custom commands are documented in [[00-Meta/Custom Commands]] which contains the complete specification.

  Available Commands

  Core Workflow

  - /process (/p) - Process inbox items, organize content, update MOCs
  - /checkpoint (/c) - Stage and commit all vault changes with git
  - /review - Comprehensive vault maintenance and cleanup
  - /status (/s) - Quick snapshot of active projects and blockers

  Analysis & Reporting

  - /weekly (/w) - Generate weekly progress reports
  - /synthesize [topic] - Create comprehensive topic analysis from all vault content
  - /align - Check strategic alignment across initiatives
  - /export [format] - Generate external documentation (wiki, reports, technical docs)

  Planning & Management

  - /planning - Epic planning assistance with timeline and dependency analysis
  - /migrate [source] [target] - Content migration with automatic link updates
  - /cleanup - Quick inbox triage without full processing

  Where They're Documented

  1. Full Documentation: [[00-Meta/Custom Commands]] - Complete specs with workflows and examples
  2. Quick Reference: [[00-Meta/README]] - Brief command list in "Working with Claude Code" section
  3. AI Instructions: [[CLAUDE.md]] - How I should interpret and execute these commands

  Access Methods

  You can:
  - Type any command directly (e.g., /process, /status)
  - Use shortcuts (/p, /c, /s, /w)
  - Read full documentation: Read the Custom Commands file
  - Get quick help: Just ask "What commands are available?"

  The commands are designed to streamline your most common vault operations into simple, memorable shortcuts!

If it isn't clear already, this effectively replaces a whole set of custom PKM software -- you can define your own processes!

You decide what your frequently used workflows are, create shortcuts for them, define how those shortcuts work, change them when needed.

The commands, the workflows, is also stored locally, version-controlled if needed, and fully owned and controlled by you.

It's hard to overstate how well this works for a variety of personal use-cases: managing information day-to-day, tracking stuff you're working on, creative writing, side-projects, all of it.