notion-sync

Synchronize Notion task updates across PR creation, branch init, and status changes.

341|48|Updated Apr 4, 2025
One-click install
npx skills add https://github.com/WellApp-ai/Well --skill notion-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: notion-sync
Source: https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/notion-sync
Command: npx skills add https://github.com/WellApp-ai/Well --skill notion-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes Notion task updates across multiple workflows and modes, ensuring consistency and traceability.

Core Features & Use Cases

  • Phase-based updates: synchronize PR links on PR creation, branch names on init, and task status on state changes.
  • Content augmentation: optionally append plan summaries or decisions to the task page body.
  • Session journaling: log session metrics to a dedicated Notion journal and link to related tasks.

Quick Start

Run notion-sync to update a Notion task page when a PR is opened or a branch is created. Example: notion-sync page_id: [task-page-id], pr_url: [PR-URL], branch_name: [branch-name], status: [Lifecycle].

Frequently Asked Questions about notion-sync

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

FAQPage Schema
How do I automatically update Notion task pages when a new pull request is created?

Notion task updates are standardized across workflows by synchronizing PR links on creation, branch names on init, and status on state changes. It utilizes Notion MCP tools like API-retrieve-a-page and API-patch-page to ensure consistency and traceability for every task.

Can I append plan summaries and session journals directly to a Notion task page body?

Notion task updates are standardized across workflows by synchronizing PR links on creation, branch names on init, and status on state changes. It utilizes Notion MCP tools like API-retrieve-a-page and API-patch-page to ensure consistency and traceability for every task.

Does the Notion MCP API support branch creation and lifecycle status synchronization?

Notion task updates are standardized across workflows by synchronizing PR links on creation, branch names on init, and status on state changes. It utilizes Notion MCP tools like API-retrieve-a-page and API-patch-page to ensure consistency and traceability for every task.

What is the best way to standardize task property updates across multiple Notion workflows?

Notion task updates are standardized across workflows by synchronizing PR links on creation, branch names on init, and status on state changes. It utilizes Notion MCP tools like API-retrieve-a-page and API-patch-page to ensure consistency and traceability for every task.

Do I need a specific page ID to start synchronizing Notion tasks during development?

Notion task updates are standardized across workflows by synchronizing PR links on creation, branch names on init, and status on state changes. It utilizes Notion MCP tools like API-retrieve-a-page and API-patch-page to ensure consistency and traceability for every task.

Why does my Notion task status fail to update when branch state changes occur?

Notion task updates are standardized across workflows by synchronizing PR links on creation, branch names on init, and status on state changes. It utilizes Notion MCP tools like API-retrieve-a-page and API-patch-page to ensure consistency and traceability for every task.