sync-context

Maintain a persistent CONTEXT.md file across AI model switches.

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/yutaoshao/agent-skills --skill sync-context-yutaoshao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-context
Source: https://github.com/yutaoshao/agent-skills/tree/main/sync-context
Command: npx skills add https://github.com/yutaoshao/agent-skills --skill sync-context-yutaoshao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Maintain a persistent project context file (CONTEXT.md) that survives AI model switches and enables clean handoffs between sessions.

Core Features & Use Cases

  • Defines a clear session protocol and sections within CONTEXT.md for ongoing work
  • Validates context structure and freshness, alerting on staleness
  • Supports progressive disclosure by offloading details to a context/ directory
  • Provides a simple init/inject/check lifecycle via dedicated scripts

Quick Start

Initialize CONTEXT.md with sync-context/scripts/sync.sh init, then start your session with sync-context/scripts/sync.sh inject and keep CONTEXT.md updated as you work.

Frequently Asked Questions about sync-context

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

FAQPage Schema
How do I maintain project context across different AI agent sessions?

You can maintain project context across different AI agent sessions by using a persistent CONTEXT.md file that survives model switches. It enforces a structured handoff protocol with freshness checks to keep project memory lean and accurate.

What is the best way to hand off ongoing work when switching AI models?

The best way to hand off ongoing work when switching AI models is to define a session protocol within a persistent context file. This approach validates context structure and freshness, alerting on staleness during cross-agent transitions.

How do I initialize and inject project memory for a new development session?

To initialize and inject project memory for a new development session, run the sync.sh init script to create CONTEXT.md, then use the sync.sh inject script at session start. Keep updating CONTEXT.md manually as your work progresses.

Can I offload detailed project context to keep the main context file lean?

Yes, you can offload detailed project context to keep the main context file lean by using progressive disclosure. This is achieved by moving detailed information into a dedicated context/ subdirectory while keeping CONTEXT.md high-level.

Does this context management approach work for long-running development sessions?

Yes, this context management approach works for long-running development sessions. It validates context structure and alerts on staleness, ensuring that your project memory remains fresh and accurate throughout extended cross-agent workflows.