# Analyzing Release Readiness

Trigger a pre-merge release readiness review on a GitHub PR, GitLab MR, or local branch.

- Repository: https://github.com/aws/agent-toolkit-for-aws (3366 stars)
- Category: Git and review
- License: Apache-2.0
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add aws/agent-toolkit-for-aws --skill analyzing-release-readiness -g -a claude-code -y`
Codex: `npx skills add aws/agent-toolkit-for-aws --skill analyzing-release-readiness -g -a codex -y`
Cursor: `npx skills add aws/agent-toolkit-for-aws --skill analyzing-release-readiness -g -a cursor -y`
Gemini CLI: `npx skills add aws/agent-toolkit-for-aws --skill analyzing-release-readiness -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add aws/agent-toolkit-for-aws`

## Description

Trigger a pre-merge release readiness review on a GitHub PR, GitLab MR, or local branch. Use when the user wants to analyze code changes for risk, correctness, and potential rollback issues before merging. Trigger words include release readiness, analyze PR, analyze MR, review PR, risk analysis, pre-merge, safe to ship, ready to merge, ready to commit, any risks, before merging, validate changes, release management.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Release Readiness Review

> **AgentSpace routing (SigV4 only):** If `list_agent_spaces` is available in your tool list and the multi-space orchestration skill has NOT been invoked yet this session, invoke it first to determine which `agent_space_id` to use. Then pass `agent_space_id` on 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 `gh` CLI, `glab` CLI, 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:**

```
Has the user provided a pull request/merge request link or ID?
├── Yes: github.com PR URL               → use "GitHub PR" flow below
├── Yes: gitlab.com MR URL               → use "GitLab MR" flow below
└── No link provided, repo name only    → use "Local GitHub/GitLab repo" flow below
```

---

### GitHub PR (github.com URL or PR reference)

The rest: https://github.com/aws/agent-toolkit-for-aws/blob/HEAD/plugins/aws-agents-for-devsecops/skills/analyzing-release-readiness/SKILL.md