Back to Vibe Coder Toolkit
Environment
Health Check
Did that deploy break something?
npx promptreports-cli healthPost-deploy health check. Production URL, Sentry errors, provider billing, Git status, DATABASE_URL. 0-100 score.
health runs after every deploy (or whenever you want). It checks: production URL responds in under 500ms, new Sentry errors since the last Vercel deploy, provider billing is still healthy (no rate limits, no suspended accounts), Git working tree is clean, DATABASE_URL is set. Each check weighted, produces a 0-100 score.
On this page
Prerequisites
- NEXTAUTH_URL or NEXT_PUBLIC_APP_URL for production URL check
- VERCEL_TOKEN to fetch last deploy timestamp
- SENTRY_AUTH_TOKEN + SENTRY_ORG + SENTRY_PROJECT for error check
Flags & Options
| Flag | Description | Default |
|---|---|---|
| --days N | Lookback for provider billing check | 7 |
| --json | JSON output | — |
| --quiet | Suppress output | — |
Examples
Default check
npx promptreports-cli healthFive checks, 10 seconds.
After deploy hook
npx promptreports-cli health --jsonPipe into Slack webhook from Vercel build hook.
Output
List of checks with OK/WARN/ERR status, check name, and detail. Overall score out of 100.
OK Production URL Responding (234ms)
OK Provider billing 5 providers — $12.45 total
WARN Sentry errors 3 unresolved issues since last deploy
OK Git status Clean working tree
OK Database URL Set
──────────────────────
Score: 80/100 (Healthy)What it reads and writes
Reads
Nothing
Writes
Nothing (read-only)
API calls
- GET https://api.vercel.com/v6/deployments?limit=1&state=READY
- GET https://sentry.io/api/0/projects/{org}/{project}/issues/?query=is:unresolved
- HEAD {production URL}
- All 10s timeout
Free vs Pro usage
Free tier
- Run after every deploy — 10 second sanity check
- Paste score in PR comments
- Include in post-merge Slack bot
Pro tier
Upgrade- Auto-run on Vercel deploy webhook — alert if score drops
- Historical health score chart
- Score correlation with specific commits (who broke it?)
- Smart recovery suggestions — rollback candidate, rollforward fix
Pro tips
- Health check is idempotent — run it 100 times, no side effects
- Score < 60 should block auto-merges in CI
- WARN is intentional — 0 errors is unrealistic; minor drift is OK