dependency-analyzer
/dependency-analyzer
Analyze dependencies for upgrade planning and migration. Use when user asks "upgrade to X", "migrate from X to Y", "what breaks if we upgrade", "iOS 17 migration", "React 18 upgrade", or planning framework/SDK upgrades.
- Author
- lis186 ↗
- Repository
- SourceAtlas ↗
- Licence
- MIT
- Last repository change
- 21.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Analyze dependencies for upgrade planning and migration. Use when user asks "upgrade to X", "migrate from X to Y", "what breaks if we upgrade", "iOS 17 migration", "React 18 upgrade", or planning framework/SDK upgrades.
Triggers from the description
Original author description
Analyze dependencies for upgrade planning and migration. Use when user asks "upgrade to X", "migrate from X to Y", "what breaks if we upgrade", "iOS 17 migration", "React 18 upgrade", or planning framework/SDK upgrades.
How it works
- When to Use
- Instructions
- Command Formats
- What User Gets
- Example Triggers
SKILL.md preview
--- name: dependency-analyzer description: Analyze dependencies for upgrade planning and migration. Use when user asks "upgrade to X", "migrate from X to Y", "what breaks if we upgrade", "iOS 17 migration", "React 18 upgrade", or planning framework/SDK upgrades. --- # Dependency Analyzer ## When to Use Trigger this skill when the user: - Is planning a framework or SDK upgrade - Wants to know migration effort for version changes - Asks about deprecated APIs or breaking changes - Needs to audit usage of a specific library - Asks "how much work to upgrade X" ## Instructions 1. Identify the upgrade path or library to analyze 2. Run `/sourceatlas:deps "<upgrade>"` with the migration description 3. Returns deprecated APIs, breaking changes, and migration checklist ## Command Formats - iOS upgrade: `/sourceatlas:deps "iOS 16 → 17"` - Android: `/sourceatlas:deps "Android API 35"` - React: `/sourceatlas:deps "React 17 → 18"` - Python: `/sourceatlas:deps "Python 3.11 → 3.12"` - Library audit: `/sourceatlas:deps "kotlinx.coroutines"` ## What User Gets - Phase 0 Rule Confirmation (preview before scanning) - Required Changes: Removable checks, deprecated APIs - Modernization Opportunities: New features available - Usage Summary: All API usage with file:line references - Third-party compatibility - Migration Checklist with effort estimates ## Example Triggers - "We need to upgrade to iOS 17, how much work?" - "What breaks if we upgrade React to 18?" - "Plan the Python 3.12 migration" - "Check our usage of AFNetworking" - "How hard is the Swift 6 migration?"
Versions
The database has no other skills named dependency-analyzer.
Database snapshot: 13.11.2026 · package version 9dab9330c49e (SHA-256 digest of the entire package)
Downloads in the last 30 days: 2 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90dev-dependency-upgrade
Use for dependency upgrades, vulnerability fixes, version conflicts, lockfiles, package managers, and migration risk. - 84migration-assistant
[UDS] 引导系统性的代码迁移、框架升级与技术现代化。 Use when: 规划框架或主版本升级、评估迁移风险、在 API 迁移前先抓取契约测试的固定样本。 Not for: 维持同一套框架的原地改善——请用 /refactor;数据库 schema 设计——请用 /database。 Keywords: migration, framework upgrade, modernization, breaking change, dependency upgrade, 迁移, 升级, 技术现代化, 破坏性变更. - 100upgrade-react-native
Use when upgrading react-native to a newer version. Handles version bumps, native project changes (Android/iOS), dependency updates, and breaking change migration. Invoke with `/upgrade-react-native <version>`. - 100dependency-migration
Plan and carry out a dependency or framework upgrade or replacement in small, verifiable steps. Use when the user asks to upgrade a major version, replace one library with another, or migrate off a deprecated package or API. - 100framework-migration-deps-upgrade
Plan incremental dependency upgrades with breaking-change analysis, migration guidance, and regression testing. Use when updating packages while controlling compatibility risk. - 95migrate-ops
Framework and language migration patterns - version upgrades, breaking changes, dependency audit, safe rollback. Use for: migrate, migration, upgrade, version bump, breaking changes, deprecation, dependency audit, npm audit, pip-audit, codemod, jscodeshift, rector, rollback,…