skills.rest
lis186
lis186COMMUNITY
Explore all skills by this author →
GitHub

dependency-analyzer

Identify upgrade paths and breaking changes for libraries, frameworks, or platforms.

46|4|Updated Nov 19, 2025
Search Tags:#codebase#dependencies#migration#upgrade#breaking-changes#deprecations
One-click install
npx skills add https://github.com/lis186/SourceAtlas --skill dependency-analyzer-lis186
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dependency-analyzer
Source: https://github.com/lis186/SourceAtlas/tree/main/plugin/skills/dependency-analyzer
Command: npx skills add https://github.com/lis186/SourceAtlas --skill dependency-analyzer-lis186

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes upgrade paths and migration impact by identifying dependencies, deprecated APIs, and breaking changes to help teams plan efficient upgrades and migrations.

Core Features & Use Cases

  • Upgrade path analysis: assess dependencies, compatibility risks, and required changes for a given library, framework, or platform.
  • Migration checklist: generates a step-by-step plan with effort estimates and file references.
  • Deprecation & breaking changes awareness: highlights deprecated APIs and likely integration challenges across ecosystems (iOS, Android, React, Python, etc.).
  • Use Case: Imagine upgrading React from 17 to 18; this Skill outlines affected modules, testing scope, and a phased rollout plan.

Quick Start

Run the command: /sourceatlas:deps "React 17 → 18" to begin a structured upgrade analysis.

Frequently Asked Questions about dependency-analyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a framework upgrade and identify breaking changes in my codebase?▼

A migration checklist for a library or platform upgrade provides a step-by-step plan with effort estimates and file references, outlining affected modules, testing scope, and a phased rollout plan to guide efficient migrations.

Can I use this to assess deprecation and migration impact for both web and mobile ecosystems?▼

Yes, you can assess deprecation and migration impact across iOS, Android, web, Python, and backend ecosystems, evaluating compatibility risks and required changes for diverse libraries and frameworks during upgrade planning.

What is the best way to estimate engineering effort for a major library version bump?▼

The best way to estimate effort for a library version bump is to analyze deprecated APIs and dependency compatibility, which delivers a per-file impact overview and an estimated migration checklist for the required platform changes.

How do I know which files will be affected when upgrading a deprecated framework API?▼

To know which files are affected when upgrading a deprecated framework API, you run an upgrade path analysis that highlights integration challenges and delivers a per-file impact overview across your codebase.

Related Skills

Explore More Software Engineering Skills→
lis186lis186
46

deps

Scan manifest files to inventory dependency versions and usage points.

Community
Advanced
msichtermanmsichterman

upgrading-expo

Plan and execute Expo SDK upgrades with dependency synchronization and validation.

Community
Intermediate
kevindreekevindree

deprecation-and-migration

Plan and execute deprecation and migration of legacy systems.

Community
Advanced
NotysotyNotysoty
9

Migration Guide Writer

Generate structured migration guides for breaking API changes.

Community
Advanced