query_dependencies
Trace dependency paths between two modules to identify connections, detect circular dependencies, and reveal shared dependencies before refactoring or modifying code.
Instructions
Trace how two modules are connected BEFORE splitting, merging, or decoupling them.
CALL THIS WHEN: • You're refactoring and need to know if two modules depend on each other • You suspect a circular dependency and want to confirm it • You're planning to extract shared code and need to see what both modules use • You need to understand why changing module A affects module B
RETURNS: Forward and reverse dependency paths between the two modules, circular dependency detection with warnings, and all shared dependencies (modules both depend on).
EXAMPLES: • "Do slack and crons have a circular dependency?" • "What's the dependency path from auth to db?" • "What do the api and workers modules have in common?" • "Why does changing utils break the notifications module?"
WHY NOT JUST READ FILES: Import statements show direct dependencies but miss transitive paths (A→B→C→D). This traces the full module graph and reveals indirect connections, circular dependencies, and shared dependencies invisible from file-level inspection.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||