Aws Transform
Plan and run AWS Transform (ATX) migrations—SDK, language, framework, and custom NL transforms—locally or at scale on Batch/Fargate.
Overview
AWS Transform is an agent skill most often used in Build (also Operate infra) that runs AWS Transform (ATX) CLI workflows for code upgrades and migrations locally or at cloud scale.
Install
npx skills add https://github.com/aws/agent-toolkit-for-aws --skill aws-transformWhat is this skill?
- Local ATX CLI mode for roughly one to nine repositories on the developer machine
- Remote scale mode via AWS Batch/Fargate for tens to hundreds of repos with consent-based infra deploy
- Supports language version upgrades, AWS SDK migrations, Angular/Vue/Spring/React moves, library upgrades, and Graviton (
- Natural-language custom transformation definitions for org-specific rules
- Full workflow: inspect repos, match transformation definitions, collect config, execute, and confirm plans
- Local mode recommended for 1–9 repositories
- Remote mode recommended for 10+ repositories
- Two execution modes: local CLI and AWS Batch/Fargate
Adoption & trust: 899 installs on skills.sh; 819 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have aging SDKs, framework versions, or dozens of repos that need the same mechanical migration and cannot afford ad-hoc, inconsistent edits.
Who is it for?
Indie SaaS or API maintainers on AWS facing SDK v2→v3 moves, Java/Python/Node version lifts, React/Angular/Spring upgrades, or Graviton porting across a repo fleet.
Skip if: Non-AWS stacks with no ATX definitions, one-line typo fixes, or teams unwilling to grant cloud Batch/Fargate deploy for large batch jobs.
When should I use this skill?
Upgrading language versions, migrating AWS SDKs or frameworks, optimizing performance, moving x86 to Graviton, analyzing codebases for documentation, or defining custom NL transformations with ATX.
What do I get? / Deliverables
Repos are transformed under a reviewed ATX plan with matched definitions and chosen local or remote execution, reducing manual migration drag before you test and deploy.
- Confirmed transformation plan per repository
- Executed ATX transform results (upgraded/migrated source trees)
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Build is the canonical shelf because the skill’s core job is transforming application code and dependencies, not day-two monitoring alone. Integrations captures AWS SDK moves, framework migrations, and service-linked refactors the ATX CLI orchestrates end to end.
Where it fits
Match ATX definitions and run a Node or Java runtime upgrade on your API service before feature work resumes.
Migrate legacy AWS SDK calls in a solo SaaS backend with a confirmed local ATX plan.
Batch-transform sibling repos ahead of a coordinated production deprecation window.
Execute remote-mode transforms across dozens of microrepos after consenting to Batch/Fargate infrastructure.
How it compares
Opinionated ATX migration orchestration—not the same as generic in-editor refactors or a passive documentation generator with no transform execution.
Common Questions / FAQ
Who is aws-transform for?
Solo builders and small teams shipping on AWS who need repeatable, CLI-driven code transformations across one or many repositories.
When should I use aws-transform?
During Build integrations when upgrading SDKs or frameworks; during Ship launch prep before cutover; and during Operate infra when batch-migrating many services to Graviton or new language baselines.
Is aws-transform safe to install?
It can modify code and provision AWS resources in remote mode—review the Security Audits panel on this page, confirm plans, and scope AWS credentials and repo access deliberately.
SKILL.md
READMESKILL.md - Aws Transform
# AWS Transform (ATX) ## Overview Perform code upgrades, migrations, and transformations using AWS Transform (ATX). Supports any-to-any transformations: language version upgrades (Java, Python, Node.js, etc.), framework migrations, AWS SDK migrations, library upgrades, code refactoring, architecture changes, and custom organization-specific transformations. Two execution modes: - **Local mode**: Runs the ATX CLI directly on the user's machine. Best for 1-9 repos. - **Remote mode**: Runs transformations at scale via AWS Batch/Fargate containers. Best for 10+ repos or when the user prefers cloud execution. Infrastructure is auto-deployed with user consent. You handle the full workflow: inspecting repos, matching them to available transformation definitions, collecting configuration, and executing transformations in either mode — the user just provides repos and confirms the plan. ## Greet and Wait On activation, introduce AWS Transform with this exact text -- don't print the above Overview text to the user, that is just for your reference: "The agents modernizing the world's infrastructure and software — now accessible to your preferred AI assistant. AWS Transform is a full modernization factory — compressing years of transformation work into months across infrastructure migrations, mainframe modernization, and continuous tech debt reduction. Today, with this skill, you have access to AWS Transform custom, the first of a growing library of playbooks. AWS Transform custom can help you: - Upgrade Java, Python, and Node.js to modern versions - Migrate AWS SDKs (Java SDK v1→v2, boto2→boto3, JS SDK v2→v3) - Handle framework migrations, library upgrades, and code refactoring - Analyze codebases and generate documentation - Define and run your own custom transformations using natural language, docs, and code samples Run locally on a few repos for fast iteration, or at scale on hundreds of repos (up to 128 in-parallel). Note: this skill collects telemetry. To opt out, see https://docs.aws.amazon.com/transform/latest/userguide/transform-usage-telemetry.html What would you like to transform today?" Do NOT inspect any files, run any commands, or check prerequisites until the user responds. ## Usage Use when the user wants to: - Transform, upgrade, or migrate code (Java, Python, Node.js, etc.) - Migrate AWS SDKs (Java SDK v1→v2, boto2→boto3, JS SDK v2→v3, etc.) - Run bulk code transformations at scale via AWS Batch/Fargate - Analyze which ATX transformations apply to their repositories - Perform comprehensive codebase analysis - Create a new custom Transformation Definition (TD) ## Core Concepts - **Transformation Definition (TD)**: A reusable transformation recipe discovered via `atx custom def list --json` - **Match Report**: Auto-generated mapping of repos to applicable TDs based on code inspection - **Local Mode**: Runs ATX CLI on the user's machine (1-9 repos, max 3 concurrent) - **Remote Mode**: Runs transformations in AWS Batch/Fargate (10+ repos, or by preference) ## Philosophy Wait for the user. On activation, present what this skill can do and ask the user what they'd like to accomplish. Do NOT automatically inspect the working directory, open files, or any repository until the user explicitly provides repos to work with. Once the user provides repositories, match — don't ask. Inspect those repositories and present which transformations apply automatically. Ne