cross-repo-reference

To analyze cross-repo dependencies, this Skill builds a visual dependency graph between multiple repositories to identify the blast radius of changes. It utilizes code intelligence to map relationships, ensuring code merges do not break downstream consumers or introduce contract incompatibilities.

The blast radius of a code change across multiple repositories is the measured impact of modifications on dependent codebases. This Skill identifies affected repositories by analyzing the dependency graph, helping developers visualize and contain the blast radius during code merges.

To check API contract compatibility across repository boundaries, this Skill analyzes protocols and APIs between multiple software repositories. It identifies potential compatibility issues by mapping cross-repo dependencies, ensuring that merging changes maintains protocol agreements and prevents breaking consumers.

Yes, you can visualize cross-repo impacts for your current branch without manual setup. By running the cross-repo-reference Skill, it automatically generates a cross-repo reference map using code intelligence, identifying dependency impacts and contract compatibility issues directly.

Yes, this dependency mapping tool works with git-kb code intelligence and meta CLI for cross-repo queries. It leverages these components to analyze dependency graphs between multiple software repositories, identify change impacts, and verify contract compatibility across repository boundaries.

The limitations of cross-repo impact analysis depend on the completeness of the dependency graph and the accuracy of the code intelligence queries. While it maps blast radius and contract compatibility, complex runtime behaviors or dynamic dependencies may require additional validation beyond static repository boundaries.