analyze_dependencies
Analyze code dependencies to identify circular references, unused imports, version conflicts, and coupling issues for technical debt assessment.
Instructions
Analyze code dependencies including circular references, unused imports, version conflicts, and coupling issues
WORKFLOW: Perfect for understanding complex code, identifying issues, and technical debt assessment TIP: Use Desktop Commander to read files, then pass content here for analysis SAVES: Claude context for strategic decisions
Input Schema
Name | Required | Description | Default |
---|---|---|---|
analysisDepth | No | Level of dependency analysis detail | detailed |
analysisType | No | Type of dependency analysis to perform | comprehensive |
checkDevDependencies | No | Include devDependencies in analysis | |
code | No | The code to analyze for dependencies (single-file analysis) | |
filePath | No | Path to single file to analyze for dependencies | |
files | No | Array of specific file paths for dependency analysis | |
ignorePatterns | No | Patterns to ignore (e.g., ["node_modules", "*.test.js"]) | |
includePackageJson | No | Include package.json analysis for version conflicts | |
language | No | Programming language for language-specific dependency patterns | javascript |
maxDepth | No | Maximum directory depth for dependency discovery (1-5) | |
projectPath | No | Path to project root for comprehensive dependency analysis |