dependency-analyzer

lis186's avatarfrom lis186

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.

⭐15stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026

When & Why to Use This Skill

The Dependency Analyzer is a specialized Claude skill designed to streamline software migration and framework upgrades. It automates the complex process of scanning codebases to identify deprecated APIs, breaking changes, and modernization opportunities across various ecosystems including iOS, Android, React, and Python. By providing detailed migration checklists, file-specific references, and effort estimates, it empowers engineering teams to plan upgrades with precision, reduce technical debt, and ensure a seamless transition between technology versions.

Use Cases

  • Framework Migration Planning: Assessing the impact of upgrading from React 17 to 18 by identifying incompatible hooks and components.
  • Mobile OS Version Updates: Evaluating required code changes and deprecated SDK calls when migrating apps to iOS 17 or the latest Android API levels.
  • Library Usage Auditing: Performing a deep-dive audit of specific libraries (e.g., AFNetworking or kotlinx.coroutines) to determine the scope of work for replacement or version bumps.
  • Language Version Upgrades: Estimating the effort and identifying breaking syntax changes when moving to newer language versions like Python 3.12 or Swift 6.
  • Technical Debt Assessment: Generating a comprehensive migration checklist and effort estimate to help project managers prioritize framework modernization.
namedependency-analyzer
descriptionAnalyze 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?"