Verified:GitHub

analyzing-release-readiness

Runs pre-merge release readiness reviews on GitHub PRs, GitLab MRs, or local branches via the AWS DevOps Agent.

1|Updated Aug 1, 2024

Search Tags:#code review #github #gitlab #risk analysis #pre-merge #release readiness #aws devops agent

One-click install

npx skills add https://github.com/obispobruno/dotfiles --skill analyzing-release-readiness-obispobruno

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: analyzing-release-readiness
Source: https://github.com/obispobruno/dotfiles/tree/main/dot_agents/skills/analyzing-release-readiness
Command: npx skills add https://github.com/obispobruno/dotfiles --skill analyzing-release-readiness-obispobruno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merging code without a structured risk assessment can introduce regressions and rollback headaches. This Skill automates a pre-merge release readiness review that analyzes code changes for risk, correctness, and rollback issues, then returns a structured report with actionable findings and suggested fixes. ## Core Features & Use Cases - PR/MR Analysis: Trigger a review directly from a GitHub PR or GitLab MR URL — fields are parsed from the link and passed to the AWS DevOps Agent, no local inspection needed. - Local Branch Workflow: For local changes, the Skill stashes uncommitted work, creates a disposable review branch, pushes it, and cleans up afterward. - Static vs. Full Analysis: Choose quick static analysis (code review, risk assessment, dependency checks) or full analysis with automated testing in a spun-up environment. - Auto-Fix Flow: After the report is saved as a markdown file, the Skill generates fixes for actionable risks and pushes them to a `feat/release-readiness-fix` branch. - Use Case: Before merging a feature branch, ask for a release readiness review; the Skill polls the job, streams progress findings, saves the report, and offers to apply fixes automatically. ## Quick Start Ask the assistant to run a release readiness review on your pull request by pasting its GitHub or GitLab URL, or name a local repository branch to analyze before merging.

Frequently Asked Questions about analyzing-release-readiness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run a release readiness review on a GitHub pull request?▼

Paste the GitHub PR URL and the Skill parses the repository, PR number, and hostname directly from the link. It passes these to the AWS DevOps Agent's create_release_readiness_review tool — no gh CLI or local inspection is needed.

How do I analyze local uncommitted changes before merging?▼

Reference the repository without a PR link and the Skill stashes your changes, creates a disposable review branch, commits a snapshot, and pushes it for analysis. After the review completes, it restores your original branch and working state.

Does the release readiness review support GitLab merge requests?▼

Yes, GitLab MR URLs on gitlab.com or self-hosted instances are supported. The Skill extracts the repository, merge request IID, and hostname from the URL and passes them under gitlabMrContent as an array of objects.

What is the difference between static analysis and automated testing in the review?▼

Static analysis (skip_automated_testing=true) runs code review, risk assessment, and dependency checks quickly. Full analysis (false) additionally spins up a testing environment, builds the code, and runs automated verification tests, which takes longer.

What happens if the AWS DevOps Agent remote server is unavailable?▼

The Skill falls back to the aws-mcp path, using AWS CLI commands like devops-agent create-backlog-task and list-journal-records directly. You select an agent space, then the same polling, reporting, and auto-fix workflow applies.

Why did my release readiness review fail immediately after starting?▼

Common causes include passing prNumber or mergeRequestIid as integers instead of strings, or not wrapping githubPrContent/gitlabMrContent in an array. If it fails fast, the Skill checks list_associations to verify the hosting service is linked to the agent space.