Deployment Readiness Review

    1

    Identify deployment blockers, schema risks, and recovery constraints through evidence-based release reviews.

    $2.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    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

    CategoryFindingClassificationImpact
    Data CompatibilityAdding NOT NULL column user_status without a default value.Supported BlockerExisting app instances will fail on writes during the migration rollout.
    Migration OrderSchema migration is set to run before the new code is healthy.Supported BlockerOld readers will crash on SELECT * if they don't expect the new column.
    Rollback RiskDestructive 'ALTER' prevents simple image revert.Conditionally AcceptableRequires manual data cleanup or pre-filled defaults to rollback.
    ConfigurationUSER_STATUS_DEFAULT env var missing in spec.Unknown VerificationNew code may throw runtime errors if this isn't in the secret store.

    Recovery Decision Tree

    1. Trigger: Migration fails or pod startup probes fail.
    2. Path A (Additive): If migration completed, keep new schema but deploy code with optional field handling.
    3. 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_DEFAULT environment variable to the Kubernetes deployment spec.
    • Provide evidence of a successful restore from the latest RDS snapshot before proceeding.
    I have reviewed the migration script (add_user_status.sql

    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

    1. Scope Definition: Supply the release diff, target environment details, and available operational evidence.
    2. Compatibility Analysis: The agent traces dependencies and verifies version-specific claims against provided documentation.
    3. Risk Classification: Findings are categorized into supported blockers, conditionally acceptable, or unknown verifications.
    4. 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.

    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. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    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

    Permissions

    Read Files
    Write Files
    Listed10 days ago
    Updated8 days ago

    What's inside

    Frequently Asked Questions

    This skill prevents production incidents by auditing release artifacts for 'silent' failures—like destructive database migrations or configuration mismatches—that traditional unit and integration tests often overlook during the deployment phase.

    The skill is agnostic and works with any stack providing versioned source code, configuration files (YAML, JSON, Terraform), and migration scripts, making it ideal for teams using rolling or blue-green deployment strategies.

    You provide the release diffs and environment configurations; the skill then performs a multi-step audit to map dependencies, evaluate rollback safety, and generate a prioritized risk report with specific post-deployment checks.

    No, this skill is designed for safety and auditing; it identifies risks and provides a decision tree for recovery but does not execute infrastructure changes, access live networks, or read sensitive secrets.

    You receive the specialized agent skill, integration guidelines for your CI/CD pipeline, and a structured reporting template designed to enforce evidence-based deployment verdicts.

    By requiring concrete evidence for every safety claim, the skill prevents the LLM from making 'safe-to-deploy' assumptions, ensuring it flags unknown risks rather than hallucinating a successful outcome.

    New in LLM Ops