odylith-sync

Refresh Odylith governance surfaces automatically when source files change.

34|3|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/odylith/odylith --skill odylith-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: odylith-sync
Source: https://github.com/odylith/odylith/tree/main/.agents/skills/odylith-sync
Command: npx skills add https://github.com/odylith/odylith --skill odylith-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically refreshes Odylith governance surfaces whenever source files change, ensuring consistency across sessions and avoiding stale surfaces.

Core Features & Use Cases

  • Automatic refresh of Odylith surfaces on file edits
  • Deterministic, governed updates with safe fallbacks
  • Use case: when a repository changes, quickly rehydrate surfaces to reflect the latest state

Quick Start

After changing a file, trigger odylith-sync to refresh governance surfaces.

Frequently Asked Questions about odylith-sync

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

FAQPage Schema
How do I automatically refresh governance surfaces when source files change?

You can automatically refresh governance surfaces when source files change by triggering a deterministic sync process that detects file edits and updates the surfaces to maintain consistency across sessions.

What is the best way to keep development workflow surfaces in sync across repositories?

Keeping development workflow surfaces in sync across repositories requires detecting file changes and applying deterministic surface refreshes to rehydrate the latest state, ensuring governed updates with safe fallbacks.

How does change detection work for deterministic surface refreshes?

Change detection for deterministic surface refreshes works by monitoring source file edits, then automatically updating the affected surfaces and synchronizing the state to prevent stale governance data across sessions.

Does odylith-sync require any special dependencies to update surfaces on file edits?

Odynlith-sync does not require any special dependencies to update surfaces on file edits, operating independently to detect changes and rehydrate governance surfaces within your existing development workflow.

When do I need to trigger a surface refresh in my development workflow?

You need to trigger a surface refresh in your development workflow whenever a repository changes, ensuring you quickly rehydrate surfaces to reflect the latest state and avoid stale governance data.