deploy-verify

Automate post-deployment health checks with Playwright across production routes.

Updated Mar 23, 2026

Search Tags:#screenshots #production #playwright #deploy #health-check #smoke-test #console-errors

Ready to run

npx skills add https://github.com/mia-cx/.agents --skill deploy-verify-mia-cx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deploy-verify
Source: https://github.com/mia-cx/.agents/tree/main/skills/deploy-verify
Command: npx skills add https://github.com/mia-cx/.agents --skill deploy-verify-mia-cx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies production deployments by automatically checking HTTP status codes, page content, console output, and capturing evidence screenshots to confirm release health.

Core Features & Use Cases

HTTP status checks across defined routes to ensure availability.
Console error capture to surface runtime issues after deploys.
Visual evidence with automated screenshots for quick verification.
Live URL testing uses Playwright against production endpoints without a local server.

Quick Start

Provide the production URL and routes to verify, then run the smoke-test script to perform automated checks.

Frequently Asked Questions about deploy-verify

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

FAQPage Schema

How do I automate post-deployment health checks for production web apps?▼

Automate post-deployment health checks by validating HTTP status codes, page content, and console output. Use Playwright to hit live production URLs, capture screenshots, and generate a per-route verdict to verify release health.

Can I capture console errors and screenshots after a production deploy?▼

Yes, you can capture console errors and screenshots after a production deploy. The Skill uses Playwright against live endpoints to record runtime console output and capture visual evidence for quick verification.

Does this smoke-test approach work for SPAs and static sites?▼

This smoke-test approach works for SPAs and static sites. It applies to production deployments across web apps, hitting live URLs to verify health for critical routes without requiring a local server.

What is the best way to verify critical routes after a release?▼

The best way to verify critical routes after a release is running automated Playwright checks against live production URLs. This validates HTTP status codes and page content, outputting a per-route verdict suitable for CI or manual review.

How do I run a production smoke-test on demand?▼

Run a production smoke-test on demand by providing the production URL and routes to verify. The script uses Playwright to hit the live URLs, capturing screenshots and console errors to confirm deployment health.

Are there limitations when testing production endpoints with Playwright?▼

A key limitation is that testing production endpoints with Playwright requires live URLs to be accessible. The Skill tests against production endpoints directly without a local server, meaning routes must be publicly available to generate a health verdict.