sync-state

Synchronize shared .agent state with local memory files.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/ysgdepaula/x-deep-os --skill sync-state
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-state
Source: https://github.com/ysgdepaula/x-deep-os/tree/main/.claude/skills/sync-state
Command: npx skills add https://github.com/ysgdepaula/x-deep-os --skill sync-state

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as a bridge between the shared state (.agent/ in the repo) and the local memory, ensuring the agent's ongoing decisions are based on a consistent, up-to-date view.

Core Features & Use Cases

  • Pull latest changes: fetches commits and updates from nightly audits or remote agents.
  • Read and reconcile state: inspects state.json, changelog, queue, and rules to detect divergences.
  • Synchronize memory: updates memory/project_architecture.md and memory/feedback_agent_rules.md when needed.
  • Present summary to user: returns a concise, readable report of the sync status and any actions taken.

Quick Start

Run the sync-state action at the start of a session to align your local memory with the shared .agent state.

Frequently Asked Questions about sync-state

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

FAQPage Schema
How do I synchronize shared agent state with local memory to maintain a single source of truth?

To synchronize shared agent state, run the sync-state action at session start to fetch latest changes, read state.json, changelog.md, queue.md and rules.md, and update local memory accordingly to maintain a single source of truth.

What is shared agent state synchronization and when do I need it?

Shared agent state synchronization bridges the .agent/ directory and local memory to ensure consistent, up-to-date views. You need it at session start or after a nightly audit to reconcile state, queue, and rules across local memory and the shared repository.

How do I reconcile local memory with a shared git repository after a nightly audit?

To reconcile local memory after a nightly audit, the sync-state action fetches latest commits, inspects state.json, changelog, queue, and rules for divergences, and updates memory/project_architecture.md and memory/feedback_agent_rules.md when needed.

Can I use sync-state with an existing git repository and local memory setup?

Yes, sync-state works with an existing git repository containing a shared .agent/ directory and local memory files. It requires no external dependencies and reads existing state.json, changelog.md, queue.md, and rules.md files to reconcile divergences.

What's the best way to keep agent state consistent across multiple remote agents?

The best way to keep agent state consistent is to run sync-state at session start. It fetches updates from nightly audits or remote agents, detects divergences in state and rules, updates local memory, and presents a concise summary report of sync status and actions taken.

Why does my local agent memory diverge from the shared repository state?

Local agent memory diverges from shared repository state when nightly audits or remote agents push updates to the .agent/ directory without updating local memory. Running sync-state reconciles these differences by reading the latest state.json, changelog, queue, and rules.