deps

Scan manifest files to inventory dependency versions and usage points.

46|4|Updated Nov 19, 2025

Search Tags:#analysis #migration #package.json #grep #upgrade #dependency

Ready to run

npx skills add https://github.com/lis186/SourceAtlas --skill deps-lis186

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deps
Source: https://github.com/lis186/SourceAtlas/tree/main/plugin/commands/deps
Command: npx skills add https://github.com/lis186/SourceAtlas --skill deps-lis186

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill analyzes dependency usage across a codebase to guide upgrades, identifying installed versions and where dependencies are used so teams can plan safe and efficient upgrades.

Core Features & Use Cases

Inventory current versions from manifest files (package.json, Podfile, build.gradle) and lock files to reveal exactly what's installed.
Locate usage points across the codebase to assess upgrade impact and migration effort.
Generate a structured YAML upgrade report including current/target versions, usage inventory, recommended changes, migration steps, and risk assessment.

Quick Start

Run the /sourceatlas:deps command with a target such as "react 17 → 18" to generate a YAML analysis for the specified dependency and review the resulting report.

Frequently Asked Questions about deps

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

FAQPage Schema

How do I analyze package.json dependency usage to plan an upgrade?▼

Analyze dependency usage by scanning manifest files like package.json and source files to inventory current versions, locate usage points, and generate a structured YAML upgrade plan with risks and steps.

Can I scan iOS Podfile and Android build.gradle files for dependency migration guidance?▼

Yes, dependency migration guidance supports JavaScript, TypeScript, iOS, and Android projects by scanning manifest files such as Podfile and build.gradle to detect installed versions and produce upgrade plans.

What is the best way to assess upgrade impact before updating a dependency?▼

Assess upgrade impact by locating usage points across the codebase to evaluate migration effort, then reviewing a generated YAML report that includes current and target versions alongside a risk assessment.

Does dependency upgrade guidance include a migration checklist?▼

Yes, dependency upgrade guidance produces a structured YAML report that includes a migration checklist, recommended changes, migration steps, and risk assessment to guide safe version upgrades.

How do I identify installed dependency versions from lock files?▼

Identify installed dependency versions by scanning manifest files and lock files to reveal exactly what is installed, providing a baseline inventory for generating upgrade guidance from official sources.