From obsidian-vault
Manages Obsidian vault as developer knowledge base: create/search/update notes with standard frontmatter, organize by projects/technologies/Claude Code, auto-capture commits/tasks/components.
npx claudepluginhub mwguerra/claude-code-plugins --plugin obsidian-vaultThis skill uses the workspace's default tool permissions.
Manage the Obsidian vault as a developer knowledge base and automatic work journal.
Manages Obsidian vault structure by organizing documents into service and work-log layers, adding files with auto-categorization and metadata, processing meeting notes, running health checks, and committing via Git.
Provides persistent Obsidian vault memory for coding agents. Auto-orients sessions with TODOs and project overviews, supports lookup of notes/patterns, and writes discoveries using commands like init, lookup, note.
Integrates Claude with Obsidian vaults for note creation, task management, knowledge organization, and project docs using CLI (1.12+), MOCs, properties.
Share bugs, ideas, or general feedback.
Manage the Obsidian vault as a developer knowledge base and automatic work journal.
Activate this skill when:
~/guerra_vault/
├── projects/ # Project-specific documentation
├── technologies/ # Technology knowledge (Laravel, React, etc.)
├── claude-code/ # Claude Code components
│ ├── agents/
│ ├── hooks/
│ ├── skills/
│ └── tools/
├── ideas/ # Feature ideas and experiments
├── personal/ # Career and learning goals
├── todo/ # Tasks and checklists
├── references/ # Bookmarks, snippets, cheatsheets
├── journal/ # Auto-captured events
│ ├── commits/ # Git commit documentation
│ ├── tasks/ # Completed task summaries
│ └── creations/ # Component creation logs
└── _archive/ # Archived notes
All notes MUST include this YAML frontmatter:
---
title: "Note Title"
description: "Brief description of the content"
tags: [tag1, tag2, category]
related: [[path/to/related-note]]
created: YYYY-MM-DD
updated: YYYY-MM-DD
---
Rules:
title: Descriptive, matches the main headingdescription: One sentence explaining the contenttags: Always include the category as a tagrelated: Wiki-link format, add related notes when relevantcreated: Set once when createdupdated: Update whenever the note changes| Command | Purpose |
|---|---|
/obsidian-vault:init | Set up vault configuration and structure |
/obsidian-vault:add <category> <title> | Create a new note |
/obsidian-vault:search <query> | Find notes by title, content, or tags |
/obsidian-vault:update <note> | Edit note frontmatter or append content |
/obsidian-vault:import <file> | Import external files with frontmatter |
/obsidian-vault:list [category] | List notes, optionally by category |
/obsidian-vault:tags [--stats] | View tags and usage statistics |
/obsidian-vault:link <note1> <note2> | Create bidirectional related links |
/obsidian-vault:archive <note> | Move note to archive |
The plugin automatically captures:
journal/commits/YYYY-MM-DD-<slug>.mdjournal/tasks/YYYY-MM-DD-<slug>.mdclaude-code/<type>s/<name>.mdjournal/creations/updated date (done automatically by scripts)--title, --content, or --tag--category to focus on specific areasWhen finishing a feature or fix:
technologies/ideas/projects/ when starting implementationreferences/frontmatter-spec.md - Detailed frontmatter specification~/.claude/obsidian-vault.json~/guerra_vault