doc

Detects stale Obsidian documentation notes and applies approved updates based on session changes.

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/quanthubbr/tron-claude-config --skill doc-quanthubbr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc
Source: https://github.com/quanthubbr/tron-claude-config/tree/main/managed/skills/doc
Command: npx skills add https://github.com/quanthubbr/tron-claude-config --skill doc-quanthubbr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project documentation drifts out of sync with code as sessions change behavior, decisions, and architecture. This Skill locates the Obsidian vault inside the repository, cross-references notes against recent code changes, and proposes concrete documentation updates that the user approves before anything is written. ## Core Features & Use Cases - Vault Discovery: Finds any folder containing .obsidian/ inside the git repo, identifies the entry note, and handles worktrees and multi-vault repositories. - Reference Auditing: Scans notes for file:line references and reports broken, ambiguous, or stale citations by diffing against commits, uncommitted changes, and new files since a given date or git ref. - Session-Driven Updates: Builds a change summary from the current conversation or the latest session-handoff note, proposes edits in a ranked table, and applies only what the user approves. - Vault Bootstrap: When no vault exists, proposes a minimal structure with context, invariants, and edge-case notes following the repository's language and conventions. - Use Case: After a refactoring session, run the doc workflow to find every note citing moved functions, verify each referenced line still matches the code, and update only the notes you confirm. ## Quick Start Ask the AI to run the doc skill to review what changed in this session and update the project documentation vault accordingly.

Frequently Asked Questions about doc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep Obsidian documentation in sync with code changes?▼

Run the doc workflow after a coding session. It locates the vault via its .obsidian folder, summarizes what changed from the conversation or latest session note, cross-references file:line citations against git changes, and proposes edits you approve before anything is written.

How to find broken file:line references in markdown notes?▼

Run doc.mjs with the refs command and a --since date or git ref. It parses backticked file:line citations in every note, resolves them against git-tracked files, and reports references to missing files or lines beyond the end of a file.

Does this work in a git worktree or a repo without a vault?▼

Yes. In a worktree created before the vault existed, it detects the vault in the main checkout and suggests updating the branch instead of creating a duplicate. With no vault at all, it offers to bootstrap a minimal structure under docs/.

What are the requirements to run the documentation audit script?▼

The script doc.mjs has no external dependencies. It requires Node.js 18 or later and git, and must run inside a git repository. It exits with code 2 outside a repo and code 3 when no vault is found.

Will the skill commit documentation changes automatically?▼

No. It never commits. After applying approved edits, it lists the changed files and suggests the project's commit flow, such as /commit-changes, leaving the commit decision to the user.