What problem does it solve?
Keep Notion documentation aligned with the repository by auditing committed git history, detecting meaningful file-level changes, and preventing manual drift between code and published docs.
Core Features & Use Cases
- Commit range audit: Collects commits in a user-specified time window and enumerates changed files.
- Zone mapping & deduplication: Maps changed files to documentation zones and cross-references existing Notion records to avoid duplicates using the doc-updater subagent.
- Review-first apply: Presents a single plannotator review for batch confirmation and then applies approved updates via Notion MCP with URL validation and per-item error handling.
- Use Case: A maintainer audits two weeks of commits after a schema change to batch-update Notion pages describing database tables and API behaviors.
Quick Start
Invoke the skill with an optional time range such as /update-doc-full 2w to generate a proposed Notion update batch, review it in plannotator, and apply approved changes.