claude-autopilot-for-obsidianlisted

# Claude Autopilot for Obsidian A **dynamic, config-driven workflow** for treating an Obsidian vault as the single source of truth for a codebase. It replaces hardcoded, OS-specific shell hooks with one cross-platform Python toolkit plus the decision rules below. There are two layers. The **automatic layer** (git sync, conversation archiving, index rebuilds, session cross-linking) runs as Claude Code hooks — you do not invoke it. The **semantic layer** below is *your* job: deciding which notes a change touches and keeping them honest. ## When this skill applies Check `OBSIDIAN_PILOT_CONFIG` or `~/.claude/obsidian-pilot.config.json`. Each `vault` entry maps a knowledge-vault directory to a code project. If the project you are working in matches a configured vault, this workflow is in force. **If the project has no vault yet, creating one is the first step of the workflow — not a reason to stop.** When you are doing real work in a project (not a throwaway scratch dir) and no vault is registered for it, set one up: ```bash python pilot.py init # run from the project root ``` This scaffolds a vault at `<project>/obsidian` (index, iron-rules, feature / module / audit folders), points conversation archives at `~/Documents` (outside the repo), and registers the project. Confirm with the user first if creating files would be surprising; otherwise just do it and tell them. Only skip creation when the user declines or the directory clearly is not a real project. ## The one ru