Add Arm enablement custom agent prompts#110
Open
ranimandepudi wants to merge 5 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an Arm enablement custom agent workflow modeled after the existing Arm migration agent, with support for both VS Code prompt files and Codex prompt files.
The new prompt evaluates OSS repositories for Arm/aarch64 readiness using Arm MCP tools, generates a maintainer-facing
arm-enablement-report.md, exports a localarm-enablement-report.pdf, and optionally applies minimal fixes when the user explicitly requests--apply-fixes.What changed
agent-integrations/vs-code/arm-enablement.prompt.mdagent-integrations/codex/arm-enablement.mdValidation
Tested locally against
etcd-io/bboltas an OSS demo repository.Generated artifacts locally:
arm-enablement-report.mdarm-enablement-report.pdfThe demo run preserved the expected findings: bbolt was assessed as ready for Arm source/build enablement,
migrate_ease_scanreported zero Go source issues forarmv8-a, no container image surface was found,linux/arm64cross-build validation passed, and benchmark/nightly workflow parity remained as the main recommendation.