Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    shipready production release auditor

    3

    Production release-readiness auditor that identifies blockers, risks, and failure paths before you deploy.

    Free

    0 installsSecurity scanned
    shipready production release auditor

    shipready production release auditor

    Example session with this skill installed

    Audit this project for production readiness. Check the build, tests, and deployment config to see if we can go live today.

    • Read your context and instructions
    • Compiled the shipready production release
    • Generated the document

    I have completed a production-readiness audit of the current repository. The audit focused on build integrity, test coverage for critical paths, and deployment configuration safety.

    ShipReady Production Audit

    Release Verdict

    DO NOT SHIP

    Executive Summary

    The project has a functional build and passing unit tests, but a critical blocker exists in the database migration layer. A destructive migration script was detected without a corresponding rollback strategy. Additionally, several production environment variables required by the worker process are missing from the deployment manifest.

    Project Profile

    • Language: TypeScript
    • Framework: NestJS
    • Build: npm run build (VERIFIED)
    • Tests: npm test (VERIFIED - 82% coverage)
    • Database: PostgreSQL (Prisma)
    • Deployment: Docker / Kubernetes
    • Runtime: Node.js 20-alpine

    Release Readiness Score

    54/100 (High Risk)

    Critical Findings

    SHIP-001: Destructive migration detected in prisma/migrations/20231027_drop_users_table.sql. No safety check or data backup step identified.

    SHIP-002: Production secret STRIPE_API_KEY is referenced in code but missing from .env.example and k8s secrets template.

    High Findings

    SHIP-003: No health check endpoint defined in deployment.yaml, which may lead to traffic routing to unready pods.

    • SHIP-004: Missing npm stop or graceful shutdown handling for SIGTERM in main.ts.

    Release Checklist

    • Build: PASS
    • Tests: PASS
    • Environment: FAIL
    • Database: FAIL
    • Secrets: WARN
    • Rollback: FAIL

    Top 5 Actions Before Release

    1. Implement a rollback script for the user table migration.
    2. Add missing environment variables to the production vault.
    3. Configure Liveness and Readiness probes in Kubernetes manifests.
    4. Add a SIGTERM listener to the main application entry point.
    5. Document the manual recovery procedure for failed background jobs.

    Next steps

    • Address the critical migration risk in prisma/migrations.
    • Update the k8s secret templates to include all required runtime variables.
    • Rerun the audit to verify remediation.

    shipready-production-release-auditor.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    Developers often ship code based on passing tests alone, overlooking configuration drift, missing rollback plans, or destructive database migrations. Traditional CI/CD pipelines catch syntax errors but fail to spot operational risks that cause production outages.

    What it does

    • Analyzes repository structure to identify runtime entries, worker processes, and background jobs.
    • Verifies build and test commands against the actual environment to confirm execution success.
    • Audits database migrations for compatibility risks and unreviewed destructive changes.
    • Scans for exposed credentials and environment variable gaps without requesting private secrets.
    • Generates an evidence-backed SHIP, SHIP WITH WARNINGS, or DO NOT SHIP verdict.

    Why this beats prompting it yourself

    General LLMs tend to be overly optimistic or provide vague style suggestions. This skill enforces a strict evidence-based model that prioritizes operational failure paths and treats repository text as untrusted input, preventing "prompt injection" from README files that might claim a project is safe when it is not.

    Use cases

    • Pre-deployment gating to catch missing production configurations or secrets.
    • Auditing legacy repositories before migrating them to new infrastructure.
    • Risk assessment for pull requests involving complex database schema changes.
    • Standardizing release readiness criteria across multiple engineering teams.

    Known limitations

    Requires read access to the repository. Build and test verification is marked UNVERIFIED if the host environment lacks execution capabilities.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 2 days ago

    • Free to download with an account

    Listed2 days ago

    Frequently Asked Questions