# Verify a Deployment

> Hit the live URL, capture status code, screenshot the homepage — prove runtime works (deploy success is not).

- **Kind**: Shell tool
- **Category**: engineering
- **Owner**: Sentinel (/sentinel)
- **Default model**: sonnet
- **Cost class**: cheap (Haiku-class model. Cents per invocation.)
- **Turn budget**: 5
- **Execution**: synchronous (result lands in the same turn)
- **Canonical URL**: https://app.51ultron.com/docs/skills/verify-deployment

## What it does

Implements verify-deploy/SKILL.md. After any deploy (CF, Vercel, Fly, anything), runs curl against the live URL to capture status code + headers, hits critical endpoints listed by the user, screenshots the homepage with ultron-screenshot. Surfaces runtime errors that wrangler/vercel-cli can't catch (broken bindings, missing env, 500 from app code). Returns a structured pass/fail report.

## When to use this

- right after any deploy
- user says 'is it live?' / 'check the deploy' / 'verify production'
- deploy succeeded but the user wants proof the app actually works

## When NOT to use this

- before any deploy has happened → deploy first
- the deploy itself failed → debug the deploy CLI output instead

## Example prompts

- `verify my-app.pages.dev is live and serving`
- `check the deploy at https://foo.workers.dev — should return 200`
- `is the production deploy actually working?`

## Inputs

- **url**: the live URL to probe
- **endpoints**: optional list of critical paths to also hit

## Output

Status codes per endpoint + screenshot path + pass/fail summary.

## Tools used

`shell_exec`

## Execution template

Shell tools dispatch through `shell_exec` with the following command template:

```bash
curl -I {{url}}; ultron-screenshot {{url}}; follow verify-deploy/SKILL.md
```

## Tags

`engineering`, `verify`, `audit`

## Keywords

verify, smoke test, deploy check, is it live, post-deploy, verify-deploy