Sync Horizon

Keeps your Claude skillpacks in sync with what actually shipped in eve-horizon, not just what the system docs say. It reads commit logs, plan statuses, code diffs, and CLI changes to figure out what's live, then dispatches parallel workers to update reference docs and skill routing. The orchestrator stays light by reading plan headers and file stats. Workers get full context for their slice. Built for the reality that features ship via feat commits with plans marked "Implemented" while docs/system/ lags behind. If you maintain skills that wrap a moving platform and need to trust the code over the documentation, this handles the tedious cross-referencing and cascade analysis.

skills.sh installs: 292
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add incept5/eve-skillpacks --skill sync-horizon --agent claude-code

Installs into .claude/skills of the current project.

Files

Sync Horizon

Synchronize eve-skillpacks with the latest state of the eve-horizon repository.

Core Insight

System docs often lag behind implementation. Features ship via feat commits with plans marked "Implemented" — but docs/system/ may not update for weeks. This sync goes to the source: plans, code changes, and commit messages tell us what actually shipped. System docs are one signal among many, not the primary driver.

Prerequisites

The eve-horizon repo must be at ../eve-horizon (sibling directory)
.sync-state.json must exist in the repo root (create from template if missing)
.sync-map.json must exist in the repo root

Architecture: Orchestrator + Parallel Workers

You (the orchestrator) discover what shipped and dispatch focused workers. Each worker handles one update in isolation with its own context budget.

The orchestrator reads lightweight signals (commit log, plan headers, file stats, CLI module list). Workers read the heavy content (plan bodies, code diffs, source docs, target files).