skills.rest
Sebdysart
SebdysartCOMMUNITY
Explore all skills by this author →
GitHub

dependency-navigator

Trace cross-repository dependency chains and assess change impact.

Updated Mar 8, 2026
Search Tags:#architecture#refactoring#impact analysis#code navigation#dependency#cross-repo
One-click install
npx skills add https://github.com/Sebdysart/omni-link-hustlexp --skill dependency-navigator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dependency-navigator
Source: https://github.com/Sebdysart/omni-link-hustlexp/tree/main/skills/dependency-navigator
Command: npx skills add https://github.com/Sebdysart/omni-link-hustlexp --skill dependency-navigator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you understand how different parts of your codebase (across multiple repositories) are connected, allowing you to trace dependencies and assess the impact of changes.

Core Features & Use Cases

  • Dependency Tracing: Follow chains of imports and calls between functions, types, and API routes across repositories.
  • Impact Analysis: Identify all entities that would be affected by a proposed change to a shared component.
  • Type Lineage: Visualize how a data type evolves across different services and identify inconsistencies.
  • Use Case: Before refactoring a shared UserProfile type, use this Skill to see everywhere it's used in the backend API, the iOS app, and any shared type definitions, highlighting any differences.

Quick Start

Use the dependency-navigator skill to find all places where the UserProfile type is used.

Frequently Asked Questions about dependency-navigator

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

FAQPage Schema
How do I trace cross-repo dependencies for a shared type?▼

Cross-repo dependency tracing follows chains of imports and calls between functions, types, and API routes across multiple repositories. It identifies everywhere a shared type is used across backend APIs and iOS apps.

What is cross-repository impact analysis for code changes?▼

Cross-repository impact analysis identifies all entities that would be affected by a proposed change to a shared component. It assesses ripple effects across your codebase to assess the full impact of refactoring.

How do I analyze type lineage across Swift, tRPC, and API routes?▼

Analyzing type lineage across Swift, tRPC, and API routes visualizes how a data type evolves across different services. It traces dependency chains and highlights inconsistencies in shared type definitions.

Do I need an ecosystem graph to perform cross-repo code navigation?▼

Yes, cross-repo code navigation requires access to an ecosystem graph containing dependencies.internal, bridges, sharedTypes, and impactPaths. This graph provides the comprehensive data needed for impact analysis.

What is the best way to assess ripple effects before refactoring shared components?▼

The best way to assess ripple effects before refactoring shared components is cross-repository impact analysis. This maps all affected entities and dependency chains across your ecosystem to prevent breaking changes.

Related Skills

Explore More Software Engineering Skills→
frankxaifrankxai
6

integration/repo-bridge

Load repo contexts and coordinate operations across FrankX ecosystem repositories.

Community
Advanced
TheBushidoCollectiveTheBushidoCollective
187

runbooks-troubleshooting-guides

Diagnose operational issues using structured troubleshooting runbooks.

Official
Basic
atman-33atman-33

multi-repo-review

Extract diffs across VSCode workspace repositories and generate a consolidated markdown review report.

Community
Advanced
SebdysartSebdysart

cross-repo-impact

Analyze cross-repository code change impacts on APIs, schemas, and shared types.

Community
Advanced