lmiranda
d2ad90d5bb
The Stop hook referenced a non-existent "internal queue" for tracking documentation drift. Each hook runs in isolation with no way to pass data between invocations, so the queue concept couldn't work. The hook was causing errors on every session end: "Stop hook error: Prompt hook condition was not met..." Changes: - Removed the Stop hook entirely - Updated PostToolUse hook to report drift immediately when found (instead of referencing non-existent queue) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
doc-guardian
Automatic documentation drift detection and synchronization for Claude Code projects.
Problem Solved
Documentation gets outdated. Functions get renamed, configs change, versions bump—but docs lag behind. This creates:
- Multiple review cycles finding stale references
- Unnecessary commits fixing docs piecemeal
- User confusion from outdated instructions
Solution
doc-guardian watches your code changes and automatically:
- Detects when changes affect documentation
- Queues updates silently (doesn't interrupt your flow)
- Syncs all doc changes in a single commit when ready
Commands
| Command | Description |
|---|---|
/doc-audit |
Full project scan - reports all drift without changing anything |
/doc-sync |
Apply all pending documentation updates in one commit |
Hooks
- PostToolUse (Write|Edit): Silently checks if code changes affect docs
- Stop: Reminds you of pending doc updates before session ends
What It Detects
- Broken References: Function/class renamed but docs still use old name
- Version Drift: Python 3.9 in docs but 3.11 in pyproject.toml
- Missing Docs: Public functions without docstrings
- Stale Examples: CLI examples that no longer work
Installation
This plugin is part of the Leo Claude Marketplace.
/plugin marketplace add https://gitea.hotserv.cloud/personal-projects/leo-claude-mktplace.git
/plugin install doc-guardian
Integration
See claude-md-integration.md for CLAUDE.md additions.