context-sync

Refresh .context/ subdirectories with current project state and report changes.

1|Updated Mar 27, 2026

Search Tags:#workflow #agents #docs #devflow #context-sync #dotcontext

Ready to run

npx skills add https://github.com/NEXUZ-SYS/devflow --skill context-sync-nexuz-sys

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: context-sync
Source: https://github.com/NEXUZ-SYS/devflow/tree/main/skills/context-sync
Command: npx skills add https://github.com/NEXUZ-SYS/devflow --skill context-sync-nexuz-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update an existing .context/ with the current project state, overwriting outdated context to keep agents and workflows aligned.

Core Features & Use Cases

Synchronizes project state into .context/docs, .context/agents, .context/skills, and .context/workflow
Detects mode (Full MCP, Lite, Minimal) and applies the appropriate synchronization strategy
Supports complete or partial scopes and reports changes to the user
Enables automatic refresh during devflow init when .context/ already exists

Quick Start

Run the context-sync skill to refresh your .context/ from the current repository state.

Frequently Asked Questions about context-sync

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

FAQPage Schema

How do I refresh project context to keep agents aligned with current repository state?▼

To refresh project context, run context-sync to overwrite outdated files in the existing .context/ subdirectories with the current repository state, ensuring agents and workflows stay aligned. It detects the operation mode and reports all applied changes.

What is .context synchronization for development workflows?▼

.context synchronization is the process of updating .context/docs, .context/agents, .context/skills, and .context/workflow directories to reflect the latest project state, keeping development workflows aligned without manual file tracking.

Can I update .context files without dotcontext MCP tools installed?▼

Yes, you can update .context files without dotcontext MCP tools by using the standalone scan option, which enables lite or minimal operation modes to synchronize your project context independently.

What is the difference between full MCP, lite, and minimal context sync modes?▼

Full MCP mode requires dotcontext MCP tools for complete synchronization, lite mode performs a standalone scan of .context/, and minimal mode executes a lightweight operation, all detecting automatically based on your environment.

Does context-sync overwrite existing files in the .context subdirectories?▼

Yes, context-sync overwrites outdated files in .context/docs, .context/agents, .context/skills, and .context/workflow subdirectories to match the current project state, producing a detailed change report of the modifications.

When should I run a project context refresh during devflow init?▼

You should run a project context refresh during devflow init when the .context/ directory already exists, enabling automatic synchronization to update existing agents, docs, skills, and workflow scopes with the current repository state.