What problem does it solve? Keeping local markdown documentation in sync with Notion requires manual copy-paste and page organization. This Skill automates pushing .giantmem docs into a structured Notion page tree (repo > worktree > feature > doc) through the local notion-multi-mcp server, with policy-driven gating so only eligible docs publish. ## Core Features & Use Cases - Policy-driven publishing: A YAML config decides which doc classes publish automatically on write (via hook) versus on user request, with frontmatter overrides and exclusion regexes. - Tree upserts with caching: Resolves parent pages by walking a cached parent_path map, creating container pages as needed, and upserts docs by the notion: URL stored in frontmatter. - Dual index surfaces: Rebuilds both a catalog page and a Docs catalog database after every push, with row pointers stored in each doc's own frontmatter. - Use Case: After finishing a design doc in .giantmem/features/auth/, say "publish to notion" and the doc appears under Claude Artifacts with its catalog row updated and the Notion URL written back to the file. ## Quick Start Publish my current .giantmem design doc to Notion and update the catalog index.
