Add Arm Migration prompt files for various AI agents#58
Add Arm Migration prompt files for various AI agents#58
Conversation
jaidev17
changed the title
|
Claude Code: |
jaidev17
changed the title
jaidev17
changed the title
jaidev17
changed the title
|
I have added an instruction in the codex prompt file to have the agent check first if the Arm MCP server is installed or not. If it is not installed, it goes over the README.md (quick start), and helps the user install the Arm MCP server. If it is installed, the agent goes ahead with the migration. |
JoeStech
left a comment
JoeStech
left a comment
There was a problem hiding this comment.
In addition to the comments I've added, please add the MCP install check to the top of each file after addressing the comments in the Codex file, thank you.
| description: Scan a project and migrate to Arm architecture | ||
| --- | ||
|
|
||
| Before starting, verify that the `arm-mcp` MCP server is installed and available. If you don't have access to the arm-mcp tools (skopeo, check_image, knowledge_base_search, migrate_ease_scan, mca, sysreport_instructions), refer to the [MCP Server Installation Guide](https://github.com/arm/mcp#quick-start) to install it. |
There was a problem hiding this comment.
Since the quick start is all about building from scratch (in fact, that section shouldn't really be called quick start), I think we need to change this to a new file that gives reduced context instructions to the model about pulling from the dockerhub image.
i.e. add a new file called agent-install-instructions.md and link to it. The file should say something like
"search online for the latest MCP configuration instructions for Codex, pull the armlimited/arm-mcp:latest container, and use the following command and args in the MCP configuration:
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"--pull=always",
"-v", "/path/to/your/workspace:/workspace",
"--name", "arm-mcp",
"armlimited/arm-mcp"
],
"
Then our instructions won't go out of date, and we don't have to maintain instructions for all the different agents.
|
|
||
| Your goal is to migrate a codebase from x86 to Arm. Use the mcp server tools to help you with this. Check for x86-specific dependencies (such as build flags, intrinsics, and libraries) and change them to Arm architecture equivalents, ensuring compatibility and optimizing performance. Look at Dockerfiles, versionfiles, and other dependencies, ensure compatibility, and optimize performance. | ||
|
|
||
| # Steps |
There was a problem hiding this comment.
why are these numbers and the rest of the files have bullets in this section?
| 2. 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 isn't compatible, change it to a compatible version. When invoking the tool, explicitly ask "Is [package] compatible with Arm architecture?" where [package] is the name of the package. | ||
| 3. 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 isn't compatible, change it to a compatible version. When invoking the tool, explicitly ask "Is [package] compatible with Arm architecture?" where [package] is the name of the package. | ||
| 4. Look at the codebase that you have access to, and determine what the language used is. | ||
| 5. // turbo |
|
|
||
| Your goal is to migrate a codebase from x86 to Arm. Use the MCP server 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, versionfiles, and other dependencies, ensure compatibility, and optimize performance. | ||
| 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. |
There was a problem hiding this comment.
why is this file different formatting than the others (no bullets, spacing different, etc)
2 participants
Added the prompt file for
Comment at the top specifying the target location of the prompt file and how to invoke it. Header specifying the name, description, agent and tools.