Notion

Access to your Notion workspace. Pull pages into the KB and push local edits back to Notion.

Setup

The notion-cli binary is included at ./scripts/notion-cli. Invoke it directly: ./scripts/notion-cli <command>

Check-in workflow

Run this workflow during each sync:

1. Commit current state — if the working tree is clean, commit to create a baseline for diffing sync changes. Skip if there are uncommitted changes you're not ready to commit.
2. Pull frontmatter-tagged files — run notion-cli pull --kb <path> to pull latest Notion content into any KB files that have frontmatter. Review the changes via git diff and update the daily note with what changed.
3. List changed pages — run notion-cli pages list --since <last-check-in> to find Notion pages edited since the last sync.
4. Review changed pages — for each changed page, run notion-cli pages get <page-id> to fetch its content. Decide if it needs to be added to or updated in the KB (use your knowledge base skill for placement).
5. Update the daily note — summarise what changed in today's changelog entry.
6. List recent comments — run notion-cli comments list --since <last-check-in> to find new discussions.
7. Process comments:
   • For straightforward comments that affect KB content, update the relevant KB items directly.
   • For open discussions or debates, surface the discussion points (grouped by page) in the daily note.
8. Update the daily note — add comment summaries and any new action items.

Secondary workflows

• Look up comments for a specific page

CLI reference

Full command reference: references/cli-commands.md

Guardrails

• When pushing to Notion, the page content will be fully replaced with the local KB content — confirm intent before running push on many pages at once.
• If a page can't be fetched or updated, report the error and continue with other pages.
• Respect rate limits — if you get 429s, back off and retry.