verify-deploy

Verifies deployed dev-cloud and virtual-smoker apps via health checks, container status, and Playwright smoke tests.

1|1|Updated Oct 3, 2021
One-click install
npx skills add https://github.com/benjr70/Smart-Smoker-V2 --skill verify-deploy-benjr70
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-deploy
Source: https://github.com/benjr70/Smart-Smoker-V2/tree/main/.claude/skills/verify-deploy
Command: npx skills add https://github.com/benjr70/Smart-Smoker-V2 --skill verify-deploy-benjr70

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After deploying to dev-cloud or the virtual-smoker device, you need a fast, consolidated answer to "is everything actually healthy?" instead of manually SSHing into hosts, checking containers, and running smoke tests one by one. ## Core Features & Use Cases - End-to-end verification: Runs existing health-check scripts for dev-cloud reachability, Tailscale Serve endpoints, and virtual-smoker device probes, then reports one consolidated pass/fail block. - Container health checks: SSHes into both hosts to confirm expected Docker containers (backend_cloud, frontend_cloud, mongo, device_service, frontend_smoker, watchtower) are healthy or running. - Playwright smoke tests: Executes browser-based frontend probes against the deployed app and captures screenshots as artifacts. - Use Case: After a nightly deploy, invoke /verify-deploy to confirm the cloud backend API, frontend, and device services all pass before declaring the release good. ## Quick Start Ask the assistant to verify the deploy and confirm dev-cloud and virtual-smoker are healthy.

Frequently Asked Questions about verify-deploy

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

FAQPage Schema
How do I verify a deployment is healthy after deploying?

Invoke /verify-deploy or ask to verify the deploy. It runs deployment-health-check.sh, device-health-check.sh, and Playwright smoke tests, then reports a consolidated PASS/FAIL block covering reachability, containers, and frontend probes.

How to check Docker container health on a remote host over SSH?

The skill SSHes into each host and runs docker ps filtered by health status, expecting three healthy containers on dev-cloud (mongo, backend_cloud, frontend_cloud) and three running containers on virtual-smoker (device_service, frontend_smoker, watchtower).

Can I verify only dev-cloud or only the virtual-smoker device?

Yes. Pass dev-cloud as an argument to skip the virtual-smoker steps, or virtual-smoker to skip the dev-cloud steps. With no argument, both targets are verified sequentially.

Why does verify-deploy report SKIPPED instead of PASS?

A row is marked SKIPPED when the underlying script cannot run, such as missing smoke dependencies, refused SSH connections, or an unreachable tailnet. The skill never reports PASS without the underlying script exiting 0.

Does verify-deploy fix or restart failing services?

No. Verification is strictly read-only. It never runs terraform apply, ansible-playbook, container restarts, or tailscale up; if the tailnet is down it asks the user to intervene.