deployment-verification

Verify post-deploy health and trigger rollback on failed checks.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/paulingham/.claude --skill deployment-verification-paulingham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment-verification
Source: https://github.com/paulingham/.claude/tree/main/skills/deployment-verification
Command: npx skills add https://github.com/paulingham/.claude --skill deployment-verification-paulingham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically verifies that a deployed service is healthy, responsive, and stable after a release, and triggers rollback if issues are detected.

Core Features & Use Cases

  • Health check verification against live endpoints to confirm 200OK responses and readiness signals.
  • Smoke testing and basic functional checks to detect critical failures before customer exposure.
  • Error-rate monitoring and rollback automation to maintain service reliability across environments.

Quick Start

Provide the deployed URL and environment to trigger health checks, smoke tests, and automatic rollback if necessary.

Frequently Asked Questions about deployment-verification

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

FAQPage Schema
How do I run post-deploy health checks after a production release?

Post-deploy health checks verify live deployment endpoints for 200OK responses and readiness signals. You provide the deployed URL and environment to trigger automatic health verification, smoke tests, and rollback decisions.

What is automatic rollback automation and when is it triggered?

Automatic rollback is triggered when post-deploy error-rate monitoring detects service instability or critical smoke test failures. It maintains service reliability by reverting unhealthy deployments in staging or production environments.

Can I use smoke tests to detect critical failures before customer exposure?

Yes, smoke testing runs basic functional checks against your live deployment to detect critical failures before customer exposure. This post-deploy verification confirms service responsiveness and stability after release.

How do I monitor error rates and emit telemetry markers after deployment?

Error-rate monitoring tracks service stability by applying post-deploy telemetry markers to your live deployment. It continuously checks for issues and emits telemetry data to inform rollback decisions.

Does this deployment verification tool require any specific dependencies?

No specific dependencies are required. You simply provide the deployed URL and environment to trigger health checks, smoke tests, and automatic rollback if necessary, applying it after your harness deploy.

What is the best way to verify service readiness in staging environments?

The best way to verify service readiness is running post-deploy health checks and smoke tests against live staging endpoints. This confirms 200OK responses and readiness signals before promoting to production.