update-doc-full

Audit git history and map changed files to Notion documentation zones.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Astrumon/Spovishun --skill update-doc-full
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-doc-full
Source: https://github.com/Astrumon/Spovishun/tree/main/.claude/skills/update-doc-full
Command: npx skills add https://github.com/Astrumon/Spovishun --skill update-doc-full

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about update-doc-full

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

FAQPage Schema
How do I batch-sync committed git changes to Notion documentation?

Batch-syncing committed git changes to Notion requires auditing repository history over a time window, mapping changed files to documentation zones, and producing proposed Notion updates for interactive batch review and approval.

What's the best way to prevent manual drift between code and published docs in Notion?

Preventing manual drift between code and published docs involves auditing committed git history, detecting meaningful file-level changes, and cross-referencing existing Notion records to avoid duplicates before applying updates.

Do I need Notion MCP APIs to apply approved documentation updates?

Yes, applying approved documentation updates requires Notion MCP APIs with URL validation to handle per-item error handling and apply the changes to Notion pages.

Can I review proposed Notion updates before they are applied?

Yes, proposed Notion updates are presented as a single plannotator review for batch confirmation, ensuring you can interactively approve changes before they are applied via the Notion MCP APIs.

How does the commit range audit map changed files to documentation zones?

The commit range audit collects commits in a user-specified time window, enumerates changed files, and maps them to documentation zones while cross-referencing existing Notion records to avoid duplicates using the doc-updater subagent.

What are the limitations of automating Notion documentation updates from git history?

Limitations include requiring git access, the doc-updater subagent, plannotator for interactive approval, and Notion MCP APIs with URL validation to apply approved updates, with per-item error handling for failed changes.