notion-sync_skill

This skill standardizes Notion task updates across modes, syncing PR links, branch names, statuses, and optional content append.
  • TypeScript

306

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill wellapp-ai/well --skill notion-sync

  • SKILL.md6.1 KB

Overview

This skill standardizes how Notion task pages and session journals are updated across automation modes. It ensures PR links, branch names, lifecycle states, and appended content are applied consistently. It also creates or updates session journal entries to capture metrics, decisions, and learnings.

How this skill works

The skill reads the target Notion task page, verifies current property values, and patches the standard fields (Github PR link, Branch name, Lifecycle/Status). If needed, it fetches block children and appends structured content like implementation plans, PR summaries, or status notes. For sessions, it searches for an existing session page by branch, then creates or updates the session entry and appends decisions and learnings, linking back to the kanban task.

When to use it

  • When pushing a PR so the task gets the PR link and plan appended.
  • When initializing work to stamp the task with the branch name.
  • Anytime an automated mode changes task status or lifecycle.
  • When appending implementation plans, summaries, or status updates to a task page.
  • After a session ends, on manual "sync session", or when a PR is created to record session metrics and decisions.

Best practices

  • Always retrieve the page first and confirm existing values before patching to avoid overwrites.
  • Keep appended content concise and use headings (e.g., Implementation Plan, Decisions, Learnings) for clarity.
  • Search sessions by branch name and last_edited_time to avoid duplicate session pages.
  • Update only the fields relevant to the current mode (PR, init, or status change).
  • Create ADRs for any decision flagged as high impact and link the ADR in the session page.

Example use cases

  • Push PR mode: add the GitHub PR URL to the task, append the PR summary, and mark status.
  • Init mode: write the newly created branch name into the task's Branch name property.
  • Session sync: record duration, loops, rework, RED count, escalations, and link decisions to the task.
  • Manual sync: append a Kaizen learning and update the session page with new metrics.
  • Automated workflow: update Lifecycle/Status when CI or deployment events occur.

FAQ

It searches the session journal database by branch name and sorts by last_edited_time; if a match exists it patches that page, otherwise it creates a new one.

What content types are safe to append to pages?

Headings, paragraphs, and bulleted list items are supported for plans, PR summaries, decisions, and learnings.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational