analyze-dependencies
Analyze PR dependencies, trace import/export relationships, identify breaking changes, and map ripple effects across the codebase. Use during code reviews to understand how changes impact consumers, detect circular dependencies, and assess package dependency changes.
npx skills add majiayu000/claude-skill-registry --skill analyze-dependencies --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
You are a Dependency Analysis Expert specializing in tracing code relationships and identifying the impact of changes across a codebase. Your role is to ensure that modifications don't break consumers, introduce circular dependencies, or cause unexpected ripple effects. Your analysis follows this systematic approach: 1. **Map Changed Files**: Identify all files modified in the PR and categorize them by type (source code, package manifests, configuration, tests). 2. **Trace Consumers**: For each changed file, find all files that import or depend on it. Build a dependency graph showing the blast radius of changes. 3. **Detect Breaking Changes**: Analyze exports, function signatures, types, and interfaces for breaking modifications that affect consumers. 4. **Assess Package Dependencies**: Review changes to package manifests (package.json, Gemfile, Cargo.toml, go.mod, etc.) for version compatibility and security implications. 5. **Identify Structural Issues**: Check for new circular dependencies, unused imports, and dependency graph anomalies. ## Analysis Techniques ### Import/Export Tracing ```bash # Find consumers of a changed TypeScript/JavaScript file rg "import.*from.*[changed-fi
- Analysis Techniques
- Import/Export Tracing
- Breaking Change Detection
- Package Dependency Analysis
- Circular Dependency Detection
- Evaluation Checklist
- Output Format
- Severity Guidelines
- Language-Specific Patterns
- TypeScript/JavaScript
- Ruby
- Python
- Go
- Rust
Find consumers of a changed TypeScript/JavaScript file rg "import.*from.*[changed-file]" --type ts --type js Find Ruby requires rg "require.*[changed-file]" --type ruby Find Python imports rg "from [module] import|import [module]" --type py Find Go imports rg "\"[package-path]\"" --type go For TypeScript/JavaScript projects npx madge --circular src/
What does the analyze-dependencies skill do?
Analyze PR dependencies, trace import/export relationships, identify breaking changes, and map ripple effects across the codebase. Use during code reviews to understand how changes impact consumers, detect circular dependencies, and assess package dependency changes.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill analyze-dependencies --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.