deploy-verify

Automates Cloudflare Workers deployment planning and post-deploy validation from git changes.

2|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/jonmumm/skills --skill deploy-verify-jonmumm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-verify
Source: https://github.com/jonmumm/skills/tree/main/deploy-verify
Command: npx skills add https://github.com/jonmumm/skills --skill deploy-verify-jonmumm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying and validating Cloudflare Workers across environments is error-prone and manual, leading to delayed releases and potential regressions. This Skill automates pre-deploy checks, environment-aware deployment, and post-deploy verification to ensure reliable, faster releases.

Core Features & Use Cases

  • Pre-deploy checks: validate TypeScript/lint, run unit and integration tests, ensure a clean git status, and detect available environments from wrangler config.
  • Environment-aware deployment: deploy to a specified environment (staging, preview) or production, and coordinate multi-environment workflows.
  • Inference-based verification: infer a verification plan from git changes, execute health checks, endpoint tests, and log monitoring to confirm changes.
  • Use Case: A team pushes a change to a Worker, the system deploys to staging, runs verification, and reports results with actionable guidance.

Quick Start

Deploy to a staging environment and run the verification workflow to validate a recent change.

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-deploy verification for Cloudflare Workers?

Automate post-deploy verification for Cloudflare Workers by inferring a verification plan from recent git changes, executing health checks, endpoint tests, and log monitoring to confirm changes. This ensures reliable releases without manual validation.

How do I deploy Cloudflare Workers to multiple environments like staging and production?

Deploy Cloudflare Workers to multiple environments by detecting available environments from the wrangler config and coordinating environment-aware workflows for staging, preview, or production. The system applies pre-deploy checks before targeting the specified environment.

Can I use this deployment workflow with a monorepo containing multiple Cloudflare Workers?

Yes, this deployment workflow supports monorepos with multiple Cloudflare Workers. It automates environment-aware deployments and applies inference-based verification across the different workers within the monorepo structure.

What pre-deploy checks are needed before deploying a Cloudflare Worker?

Pre-deploy checks for a Cloudflare Worker include validating TypeScript and lint, running unit and integration tests, ensuring a clean git status, and detecting available environments from the wrangler config before execution.

What is the best way to validate environment configuration before a Cloudflare Worker deployment?

Validate environment configuration by detecting available environments from the wrangler config during pre-deploy checks. This ensures environment-aware deployment coordinates correctly across staging, preview, and production targets.

Why does my Cloudflare Worker deployment fail end-to-end checks in a CI pipeline?

End-to-end checks for Cloudflare Worker deployments fail due to incomplete pre-deploy validations, undetected environment config mismatches, or unverified git changes. Automating inference-based health checks and log monitoring resolves these manual gaps.