deploy-verify

Verify deployments with post-merge canary checks against a target URL.

2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/hamzaPixl/pixl-ai --skill deploy-verify-hamzapixl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-verify
Source: https://github.com/hamzaPixl/pixl-ai/tree/main/packages/crew/skills/deploy-verify
Command: npx skills add https://github.com/hamzaPixl/pixl-ai --skill deploy-verify-hamzapixl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures newly merged changes are actually running in production by performing automated post-merge verification to detect downtime, errors, slow responses, missing content, or unhealthy APIs before users are impacted.

Core Features & Use Cases

  • Deployment detection & wait: Polls CI/deploy workflows and waits for a deploy to complete before running checks.
  • Canary checks: Validates page load, response time thresholds, key content presence, API health endpoints, header anomalies, and SSL status.
  • Failure handling: Reports pass/warn/fail summaries and optionally performs a safe auto-revert of the last merge commit when critical failures are detected.
  • Use Case: Run after a PR merge to confirm the production URL is reachable, returns expected content, and that health endpoints report OK, reverting the merge if the site is down.

Quick Start

Run deploy-verify against the production URL or merged PR number to wait for deploy completion, run canary checks, and optionally auto-revert on critical failures.

Frequently Asked Questions about deploy-verify

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

FAQPage Schema
How do I verify a deployment after merging a PR to ensure the production URL is healthy?

Post-merge deployment verification polls CI workflows, waits for completion, then runs canary checks against the production URL to validate HTTP status, response times, content presence, API health endpoints, and SSL status.

Can I automatically revert a git merge commit if post-merge health checks detect downtime?

Yes, post-merge canary checks can optionally perform a safe auto-revert of the last merge commit when critical failures like downtime, missing content, or unhealthy APIs are detected after a deployment.

What checks are included in a post-merge canary deployment validation?

Canary deployment validation includes page load verification, response time threshold checks, key content presence, API health endpoint polling, HTTP header anomaly inspection, and SSL status confirmation.

How do I wait for a CI deploy workflow to finish before running health checks on my web application?

Deployment detection polls CI and deploy workflows, waiting for the deployment to complete before executing canary health checks against the target URL to confirm availability and correctness.

Does deploy-verify work without any external dependencies or components?

Yes, deploy-verify operates independently with no required dependencies or components, performing post-merge canary checks and optional git-based auto-revert procedures directly against the target URL.

What is the best way to handle deployment failures and report post-merge validation results?

Failure handling reports pass, warn, and fail summaries after canary checks, and optionally triggers a safe auto-revert of the last merge commit when critical deployment failures are detected.