Deps
Analyze dependency usage for library/framework/SDK upgrades
Install
/plugin marketplace add lis186/SourceAtlasThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add lis186/SourceAtlas --skill depsgit clone --depth 1 https://github.com/lis186/SourceAtlas.git /tmp/SourceAtlas
mkdir -p ~/.claude/skills
cp -r /tmp/SourceAtlas/plugin/commands/deps ~/.claude/skills/depsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# SourceAtlas: Dependencies > **Constitution**: [ANALYSIS_CONSTITUTION.md](../../../ANALYSIS_CONSTITUTION.md) v1.1 ## Context **Target:** $ARGUMENTS (library name, version upgrade, or iOS minimum version) **Goal:** Analyze dependency usage and provide upgrade guidance **Time Limit:** 5-15 minutes ## Quick Start 1. **Check cache** (skip if `--force` flag present) 2. **Detect version** from manifest files (package.json, Podfile, etc.) 3. **Search for upgrade rules** using WebSearch (if version upgrade) 4. **Find all usage points** using grep/Glob 5. **Categorize usage** by API type 6. **Generate YAML report** following [output-template.md](output-template.md) 7. **Verify output** using [verification-guide.md](verification-guide.md) 8. **Auto-save** to `.sourceatlas/deps/` ## Your Task You are analyzing dependency usage to help users understand: 1. **Current state**: Which version is installed, where it's used 2. **Upgrade impact**: What needs to change for version upgrades 3. **Migration path**: Step-by-step upgrade checklist 4. **Risk assessment**: How complex is the upgrade ### Upgrade Types You Handle | Input Pattern | Type | Focus | |--------------|------|-------| | `iOS 17`, `iOS 16 → 17` | iOS Minimum Version Upgrade | Removable `#available`, deprecated APIs, new opportunities | | `iOS SDK 26`, `Xcode 16` | SDK/Compiler Upgrade | Compilation warnings, Swift version, new syntax |
Details
- Skill name
deps- Repository
- lis186/SourceAtlas
- Path
plugin/commands/deps/SKILL.md- License
- MIT
- Repo updated
- 22 October 2026
FAQ
What does the Deps skill do?
Analyze dependency usage for library/framework/SDK upgrades
How do I install the Deps skill?
Claude Code plugin: /plugin marketplace add lis186/SourceAtlas. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Deps popular?
It lives in lis186/SourceAtlas, which has 49 GitHub stars and 4 forks.
Related skills
Code Flow Tracer
49lis186/SourceAtlas
Trace code execution paths and data flow. Use when user asks "how does X work", "what happens when X", "trace the flow of X", "where does data come from", or needs to understand feature implementation.
Codebase Overview
49lis186/SourceAtlas
Quickly understand a new codebase's architecture, tech stack, and patterns. Use when user asks "what is this project", "project overview", "how is this codebase structured", "what tech stack", or when onboarding to a new codebase.
Dependency Analyzer
49lis186/SourceAtlas
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.
History Analyzer
49lis186/SourceAtlas
Analyze git history for hotspots, coupling, and knowledge distribution. Use when user asks "who knows this code", "what files change most", "hotspots", "bus factor", "knowledge silos", or needs to understand code evolution.
Impact
49lis186/SourceAtlas
Analyze the impact scope of code changes using static dependency analysis
Impact Analyzer
49lis186/SourceAtlas
Analyze what code will be affected by changes. Use when user asks "what will break if I change X", "impact of changing X", "dependencies of X", "is it safe to modify X", or before making significant code changes.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.