migration-analyzer

Scan infrastructure and source code to map AWS dependencies and generate migration artefacts.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/joleques/northstar-ai --skill migration-analyzer-joleques
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migration-analyzer
Source: https://github.com/joleques/northstar-ai/tree/main/.codex/skills/migration-analyzer
Command: npx skills add https://github.com/joleques/northstar-ai --skill migration-analyzer-joleques

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maps dependencies and external integrations across a bounded context to enable safe AWS account migrations.

Core Features & Use Cases

  • Scan /infra to extract environment variables, ARNs, SQS/SNS resources, and Kubernetes endpoints from a repository pair.
  • Reverse-engineer application code to locate consumption points (HTTP clients, AWS SDK, gRPC stubs) and build a dependency graph.
  • Output migration artefacts (matriz-impacto.md, alertas-aws.md, migration-waves.md) into an adjacent analise/ folder to guide deployment waves.

Quick Start

Provide the absolute path to the context directory and run the migration analysis to generate the artefacts.

Frequently Asked Questions about migration-analyzer

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

FAQPage Schema
How do I map external dependencies for an AWS account migration?

To map external dependencies for an AWS account migration, scan your /infra directory and source code to extract ARNs, environment variables, and inter-service dependencies to build a dependency graph for safe migration planning.

What is context mapping for AWS migration planning?

Context mapping for AWS migration planning is the process of scanning bounded contexts to identify external integrations like SQS, SNS, and Kubernetes endpoints to generate a dependency graph for safe account migrations.

How do I generate migration artefacts for bounded contexts?

Generate migration artefacts for bounded contexts by running a read-only analysis on your repository pair to output impact matrices, AWS alerts, and migration waves into an adjacent analise/ folder.

Can I reverse-engineer application code to find AWS SDK consumption points?

Yes, you can reverse-engineer application code to find AWS SDK consumption points by locating HTTP clients, AWS SDK calls, and gRPC stubs to map inter-service dependencies without modifying source code.

Does the dependency graph analysis modify my existing source code?

No, the dependency graph analysis enforces non-modification of source code by requiring read-only access to scan /infra and application code, outputting all migration artefacts into an adjacent folder.