production-readiness-review

Drive a real browser over a live site and check the database for connection storm signatures.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/NewEarthAI/vibecode-project-template --skill production-readiness-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: production-readiness-review
Source: https://github.com/NewEarthAI/vibecode-project-template/tree/main/.claude/skills/production-readiness-review
Command: npx skills add https://github.com/NewEarthAI/vibecode-project-template --skill production-readiness-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires e2e-quick, get_logs, verify-shipped, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill post-deploys to verify that changes have not broken the live site for real users, catching regressions that automated checks might miss.

Core Features & Use Cases

  • Real Browser Testing: Drives a real browser over the live site to check for rendering issues, errors, and data call problems.
  • Database Check: Scans the database for connection storm signatures that indicate issues like pool exhaustion or statement timeouts.
  • Honest Coverage Verdict: Provides a clear, non-deceptive assessment of the deployed change's impact on the site.

Quick Start

Run the production-readiness-review skill with the diff range 'origin/main...HEAD' and the live site URL 'https://example.com'.

Frequently Asked Questions about production-readiness-review

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

FAQPage Schema
How do I verify post-deployment site integrity and catch regressions on a live site?

Run a post-deployment verification tool that drives a real browser over the live site to detect rendering issues, errors, and data call problems, catching regressions automated checks might miss.

What is database connection storm signature detection in production verification?

Database connection storm signature detection scans the database logs for issues like pool exhaustion or statement timeouts, using log analysis to indicate underlying production database problems.

Can I run real browser testing in production without risking data mutations?

Yes, this production verification handles the live site in a read-only manner, ensuring no mutations or auto-fixes are applied during real browser testing and database checks.

What's the best way to check for deploy and file drift after a release?

Checking for deploy and file drift requires comparing the shipped state against expected files using a verification tool that emits an honest coverage verdict based on the deployed changes.

Do I need e2e-quick and get_logs to run a production readiness review?

Yes, you need e2e-quick for the real browser drive, get_logs for the database connection storm check, and verify-shipped for deploy and file drift detection.