sync-check

To detect drift between active migrations and sub-repo states, run the /sync-check command. This action pulls the current state across registered sub-repos, compares it against active migrations, and flags any synchronization discrepancies for immediate review.

Monitoring workflow consistency across software components requires comparing active migrations to current repository states. The sync-check mechanism pulls current sub-repo states, highlights any drift, and provides a comprehensive overview to ensure cross-repo workflow consistency.

Yes, you can use sync-check to orchestrate cross-repo workflows without external dependencies. The Skill operates independently using internal scripts to pull sub-repo states, identify synchronization drift, and report discrepancies across your software components.

To quickly check sub-repo synchronization status, execute the /sync-check command. This immediately refreshes the state data, compares your registered sub-repos against active migrations, and highlights any existing drift or inconsistencies in a comprehensive overview.

You need to run drift detection for sub-repo monitoring whenever you are orchestrating cross-repo workflows and must ensure consistency across software components. Running /sync-check identifies any discrepancies between active migrations and current sub-repo reality before inconsistencies escalate.