notion-sync

Notion Sync Skill

Standardize how Notion tasks are updated across all modes.

When to Use

• Push PR mode: update PR link and append plan
• Init mode: update branch name
• Any mode updating task status
• Appending content to task pages

Phases

Phase 1: Retrieve Task Page

Fetch current task state:

API-retrieve-a-page:
  page_id: [task-page-id]

Verify the page exists and note current field values.

Phase 2: Update Standard Fields

Update properties based on context:

Available fields:

Field	Type	When to Update
Github PR link	url	On PR creation
Branch name	rich_text	On branch creation
Lifecycle/Status	select	On state changes

API call:

API-patch-page:
  page_id: [task-page-id]
  properties:
    "Github PR link": { url: "[PR-URL]" }
    "Branch name": { rich_text: [{ text: { content: "[branch-name]" }}]}

Phase 3: Append Content (Optional)

If content needs to be added to the page body:

Get existing blocks:

API-get-block-children:
  block_id: [page-id]

Append new content:

API-patch-block-children:
  block_id: [page-id]
  children: [
    {
      "type": "heading_2",
      "heading_2": { "rich_text": [{ "text": { "content": "Implementation Plan" }}]}
    },
    {
      "type": "paragraph",
      "paragraph": { "rich_text": [{ "text": { "content": "[plan-content]" }}]}
    }
  ]

Content types to append:

• Implementation plans (from Plan mode)
• PR summaries (from Push PR mode)
• Status updates

Phase 4: Confirm Sync

Verify the update was successful:

API-retrieve-a-page:
  page_id: [task-page-id]

Check that updated fields reflect new values.

---

Phase 5: Session Journal Sync (NEW)

Sync session metrics and decisions to Session Journal database.

When to Run

• After PR is created (via push-pr.mdc)
• On manual "sync session" command
• On session abandon

5.1: Gather Session Data

Collect from session-status skill:

• Duration, loops, rework, waiting, RED count, escalations