cross-repo-cache

Caching cross-repo coordinator results prevents redundant agent executions by comparing current peer repository git hashes against stored hashes from the last run, returning a cache hit or miss status to control re-runs.

Git hash comparison for cross-repo cache validation checks current peer repository git hashes against stored hashes from the last coordinator run, triggering before peer discovery in Phase 1.4.1 to return a cache hit or miss status.

You should use a cross-repo cache to skip coordinator runs in multi-repository projects when peer repositories have not changed since the last coordination, saving significant processing time by avoiding unnecessary Sonnet agent launches.

CROSS_REPO_CACHE_HIT and CROSS_REPO_CACHE_MISS are output control signals indicating whether stored coordinator results are still valid, determining whether the system should reuse existing results or re-run the coordinator.

You do not need any external dependencies to validate cached cross-repo coordinator results, as the skill operates independently using internal scripts to compare git hashes and trigger automatically during Phase 1.4.1.