context-sync

Collect GitHub PRs, issues, commits, and Notion tasks into a sync document.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/jjub0217/claude-code-skills --skill context-sync-jjub0217
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-sync
Source: https://github.com/jjub0217/claude-code-skills/tree/main/skills/context-sync
Command: npx skills add https://github.com/jjub0217/claude-code-skills --skill context-sync-jjub0217

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Notion and GitHub information often exist in separate tools, making it hard to maintain a single source of truth for task status and daily planning.

Core Features & Use Cases

  • Collects and merges GitHub PRs, issues, and commits with Notion TASK DISTRIBUTION and Daily Scrum data.
  • Generates a unified sync document and a Daily Scrum page (Notion or local Markdown) to keep the team aligned.
  • Supports optional Notion integration and local fallback to maintain workflows when Notion is unavailable.

Quick Start

Start the context-sync skill to generate a synced document and a Daily Scrum using your GitHub and Notion configurations.

Frequently Asked Questions about context-sync

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

FAQPage Schema
How do I sync Notion and GitHub data for daily scrum reporting?

Syncing Notion and GitHub data for daily scrum reporting involves collecting PRs, issues, commits, and Notion TASK DISTRIBUTION entries to generate a consolidated sync document and Daily Scrum page.

What is the best way to automate GitHub PR and issue tracking with Notion?

Automating GitHub PR and issue tracking with Notion requires aligning GitHub and Notion data sources automatically, merging development activity with task distribution entries to maintain a single source of truth.

Can I generate a daily scrum document from GitHub commits without Notion?

Generating a daily scrum document without Notion is supported through a local fallback to Markdown, maintaining workflow continuity by producing a consolidated sync document even when Notion integration is unavailable.

Does GitHub and Notion synchronization work for team task distribution tracking?

GitHub and Notion synchronization works for team task distribution tracking by collecting and merging Notion TASK DISTRIBUTION data with GitHub commits and PRs, producing a unified document that keeps the entire development team aligned on project status.

What are the limitations of automated Notion and GitHub sync documents?

Automated Notion and GitHub sync documents require optional Notion integration to output to Notion pages directly, meaning workflows without Notion configured must rely on local Markdown fallback generation for reporting.

Do I need a Notion API key to generate a consolidated sync document from GitHub?

A Notion API key is needed for Notion integration to generate and push the consolidated sync document to Notion directly, but the workflow supports a local Markdown fallback to maintain document generation when Notion is unavailable.