Deployment Readiness Review
Identify deployment blockers, schema risks, and recovery constraints through evidence-based release reviews.
$2.99
Works with the AI Agents you already use
Deployment Readiness Review
Example session with this skill installed
Review this diff for a Postgres migration and K8s deployment. We are adding a 'required' column to the users table. Here is the migration script and the updated deployment spec.
- Read your context and instructions
- Compiled the deployment readiness review
I have reviewed the migration script (add_user_status.sql) and the deployment manifest (web-deploy.yaml). The review identifies a critical blocker for zero-downtime rolling updates.
Deployment Readiness Report
| Category | Finding | Classification | Impact |
|---|---|---|---|
| Data Compatibility | Adding NOT NULL column user_status without a default value. | Supported Blocker | Existing app instances will fail on writes during the migration rollout. |
| Migration Order | Schema migration is set to run before the new code is healthy. | Supported Blocker | Old readers will crash on SELECT * if they don't expect the new column. |
| Rollback Risk | Destructive 'ALTER' prevents simple image revert. | Conditionally Acceptable | Requires manual data cleanup or pre-filled defaults to rollback. |
| Configuration | USER_STATUS_DEFAULT env var missing in spec. | Unknown Verification | New code may throw runtime errors if this isn't in the secret store. |
Recovery Decision Tree
- Trigger: Migration fails or pod startup probes fail.
- Path A (Additive): If migration completed, keep new schema but deploy code with optional field handling.
- Path B (Rollback): If migration failed, revert pod spec immediately; verify DB state for partial schema changes.
Next steps
- Update the migration to add the column as NULLABLE first, or provide a constant DEFAULT.
- Add the missing
USER_STATUS_DEFAULTenvironment variable to the Kubernetes deployment spec. - Provide evidence of a successful restore from the latest RDS snapshot before proceeding.
Connects securely to your tools. The creator never sees your data.
About this skill
Avoid production incidents by identifying deployment blockers before you ship. This skill conducts a rigorous review of your release artifacts, configuration changes, and operational evidence to spot compatibility issues that automated tests often miss. It focuses on the transition phase between development and production, specifically looking for destructive schema changes, dependency mismatches, and rollback constraints.
What it does
- Dependency Tracing maps artifact identities, configuration names, and data schema compatibility to ensure environmental alignment.
- Rollback Assessment identifies destructive operations that prevent app-only rollbacks and evaluates data loss risks.
- Migration Review analyzes rolling-deployment compatibility for old and new readers/writers during backfill or cutover phases.
- Evidence Gap Analysis flags missing verification items and distinguishes between evidenced blockers and unknown risks.
- Recovery Mapping generates a decision tree for stop triggers and recovery alternatives based on reviewed proposals.
How it works
- Scope Definition: Supply the release diff, target environment details, and available operational evidence.
- Compatibility Analysis: The agent traces dependencies and verifies version-specific claims against provided documentation.
- Risk Classification: Findings are categorized into supported blockers, conditionally acceptable, or unknown verifications.
- Report Delivery: Receive a prioritized report including prerequisites and targeted post-deployment smoke checks.
Frameworks & tools
Works with any stack providing versioned source code, configuration files (YAML, JSON, Terraform), and migration scripts. It is designed for CI/CD environments using rolling updates or blue-green deployments.
Why this beats prompting it yourself
Generic prompts often miss the nuances of "expand and contract" migrations or fail to distinguish between a backup's existence and its restore capability. This skill enforces a strict evidence-based workflow that prevents the LLM from hallucinating "safe-to-deploy" verdicts without concrete proof.
Use cases
- Reviewing complex SQL migrations for backward compatibility with running app instances.
- Verifying configuration flag alignment across staging and production environments.
- Auditing a release for "point of no return" operations that require specific recovery steps.
Known limitations
Does not perform live infrastructure actions, network requests, or secret reading. Reports are limited by the quality of sanitized evidence provided.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for LLM Ops.
Cannot access live environments or read secrets. Does not perform deployments or migrations. Requires sanitized evidence and configuration examples to produce accurate findings.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 10 days ago