dependency-analyzer
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.
What this skill does
# 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?"
Related in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.