dependency-analyzer_skill

Overview

This skill analyzes project dependencies and produces a clear plan for upgrades and migrations. It identifies deprecated APIs, breaking changes, and compatibility issues, then generates a prioritized migration checklist with effort estimates. Use it to reduce upgrade risk and scope the work required for framework, runtime, or library version changes.

How this skill works

Provide the target upgrade or the library you want audited, and the skill runs a codebase scan to locate API usage and dependency footprints. It reports deprecated or removed APIs, potential breakages, third‑party compatibility notes, and modernization opportunities. The output includes file:line references for each finding and a phased migration checklist with estimated effort.

When to use it

• Planning a framework or SDK version upgrade (e.g., iOS 16 → 17, React 17 → 18).
• Assessing migration effort between runtime versions (e.g., Python 3.11 → 3.12).
• Auditing project usage of a third‑party library (e.g., AFNetworking, kotlinx.coroutines).
• Understanding breaking changes and deprecated APIs before starting work.
• Estimating effort and prioritizing tasks for an upgrade project.

Best practices

• Start with a dry run or rule confirmation to preview what will be scanned.
• Run the analyzer early in planning to inform timelines and staffing.
• Review file:line findings with maintainers to validate false positives.
• Prioritize fixes that unblock CI and tests before widespread refactors.
• Combine dependency analysis with automated tests to measure regressions.

Example use cases

• Scan a codebase for iOS 17 migration issues and produce a phased checklist.
• Audit all usages of a library to determine if removal or upgrade is feasible.
• Estimate work to move a backend from Python 3.11 to 3.12 and list risky APIs.
• Check React 18 compatibility and surface async rendering or API breakages.
• Validate third‑party SDK compatibility with a planned platform upgrade.