analyzing-release-readiness
Installation
SKILL.md
Release Readiness Review
AgentSpace routing (SigV4 only): If
list_agent_spacesis available in your tool list and the multi-space orchestration skill has NOT been invoked yet this session, invoke it first to determine whichagent_space_idto use. Then passagent_space_idon all tool calls below. For bearer token auth this is unnecessary — the token is already scoped to one space.
Run a release readiness review via the AWS DevOps Agent. Analyzes a code change for risk, correctness, and potential rollback issues. Returns a structured report with actionable findings.
Rules:
- If a PR/MR URL is provided: Extract ALL fields from the URL. Do NOT inspect the local workspace or git state.
- NEVER use
ghCLI,glabCLI, or any external tool to fetch PR/MR details. All required fields (repository, prNumber/mergeRequestIid, hostname) MUST be parsed directly from the URL or user input. The DevOps Agent fetches the content itself — you only need to pass identifiers. - Only use the local workspace flows when the user references a repository or package without a PR/MR link.
Gathering execution parameters
Infer everything automatically from the user's request — do not ask for parameters that can be derived.
Input source decision tree: