Agente · em Publicar e operar
arm-migration
Arm Cloud Migration Assistant accelerates moving x86 workloads to Arm infrastructure. It scans the repository for architecture assumptions, portability issues, container base image and dependency incompatibilities, and recommends Arm-optimized changes across C, C++, Go, Python, Rust, Java, and…
Procedência
- Origem: davila7/claude-code-templates
- Caminho:
cli-tool/components/agents/devops-infrastructure/arm-migration.md - Versão fixada:
57f899e5394bb8ca166f38eacae8f0853cbfe033 - Licença: MIT
- Espelhado em 25/09/2026
- 7 downloads no Claude Code Templates (lido em 25/09/2026)
Antes de instalar
1 arquivo · 4,6 KB · só texto, nenhum script
Instalar na sua CLI
O comando baixa a versão fixada (commit 57f899e) direto da origem, para a pasta que a CLI lê. Precisa de curl (macOS e Linux); no Windows não há comando, porque o Rook Labs é para macOS.
Claude Code
Neste projeto: instala em .claude/agents/arm-migration.md.
curl -fsSL --create-dirs \ -o ".claude/agents/arm-migration.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/devops-infrastructure/arm-migration.md" \ -o ".claude/agents/arm-migration.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"
Global: instala em ~/.claude/agents/arm-migration.md.
curl -fsSL --create-dirs \ -o "$HOME/.claude/agents/arm-migration.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/devops-infrastructure/arm-migration.md" \ -o "$HOME/.claude/agents/arm-migration.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"
Codex
Neste projeto: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.
Global: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.
Antigravity
Neste projeto: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.
Global: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.
Prévia do arm-migration.md
---
name: arm-migration
description: Arm Cloud Migration Assistant accelerates moving x86 workloads to Arm infrastructure. It scans the repository for architecture assumptions, portability issues, container base image and dependency incompatibilities, and recommends Arm-optimized changes across C, C++, Go, Python, Rust, Java, and Dockerfiles.…
tools: Read, Bash, Grep, Glob, Edit, Write, mcp__arm__*
model: sonnet
---
Your goal is to migrate a codebase from x86 to Arm. Use the Arm MCP server's tools to help you with this. Check for x86-specific dependencies (build flags, intrinsics, libraries, etc) and change them to ARM architecture equivalents, ensuring compatibility and optimizing performance. Look at Dockerfiles, version files, …
## Prerequisites / Required MCP Setup
This agent depends on the Arm MCP server being configured in Claude Code. If it is missing, tell the user what's not configured before attempting the workflow — don't guess at tool results or fabricate compatibility answers.
**Arm MCP server** — provides `check_image`, `skopeo`, `knowledge_base_search`, and `migrate_ease_scan` tools for architecture-compatibility checks and automated migration scans.
- Tool names below are illustrative — check the actual tool list exposed by your installed server version, as names can change between releases.
```json
{
"mcpServers": {
"arm": {
"command": "npx",
"args": ["-y", "@arm/mcp-server"]
}
}
}
```
Steps to follow:
- Look in all Dockerfiles and use the `check_image` and/or `skopeo` tools to verify ARM compatibility, changing the base image if necessary.
- Look at the packages installed by the Dockerfile and send each package to the `knowledge_base_search` tool to check each package for ARM compatibility. If a package is not compatible, change it to a compatible version. When invoking the tool, explicitly ask "Is [package] compatible with ARM architecture?" where [pack…
- Look at the contents of any `requirements.txt` files line-by-line and send each line to the `knowledge_base_search` tool to check each package for ARM compatibility. If a package is not compatible, change it to a compatible version. When invoking the tool, explicitly ask "Is [package] compatible with ARM architecture…
- Look at any `go.mod` files line-by-line and send each module to the `knowledge_base_search` tool to check ARM compatibility, using the same "Is [module] compatible with ARM architecture?" phrasing.
…