菜单
Read-only deployment verification for Rico. Check, verify, confirm, status, health, stale, deployed, commit, Render, Vercel, production. Use when asked to check if Rico is deployed, confirm the backend is live, verify Render is up to date, or check production health.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Accessibility audit for Rico Hunt. Run contrast checks and review alt text, focus states, ARIA labels, and keyboard navigation in frontend code.
Read-only audit of Rico Hunt AI provider routing. Verify RICO_AI_PROVIDER env var, fallback chain, and provider health without calling live AI APIs.
Verify Rico Hunt authentication rules. Check JWT cookie usage, signup role enforcement, protected route isolation, and no request body user_id.
Verify Rico Hunt chat flow. Inspect public chat session isolation, rate limits, authenticated chat routing, and public session prefixing.
Read-only database health check for Rico Hunt. Verify DATABASE_URL connectivity, key tables, and row counts without exposing user data or mutating anything.
Verify Rico Hunt required environment variables are set without exposing values. Check backend, frontend, and admin/dev env vars.
| name | deploy-rico |
| description | Read-only deployment verification for Rico. Check, verify, confirm, status, health, stale, deployed, commit, Render, Vercel, production. Use when asked to check if Rico is deployed, confirm the backend is live, verify Render is up to date, or check production health. |
Read-only deployment verification for Rico Hunt. Checks whether the Render backend and Vercel frontend match origin/main, reports health status, and prints safe next steps. Never deploys. Never changes env vars. Never touches Neon, Stripe, JotForm, or any production DB.
The driver is .claude/skills/deploy-rico/check.sh.
| Check | Endpoint | Purpose |
|---|---|---|
| GitHub commit | git fetch origin main | Source of truth for expected commit |
Render /version | rico-job-automation-api.onrender.com/version | Deployed commit, env, app name |
Render /health | rico-job-automation-api.onrender.com/health | Backend liveness |
| Vercel proxy | ricohunt.com/proxy/health | Frontend → backend proxy rewrite working |
| Vercel root | ricohunt.com/ | Frontend itself is up |
bash .claude/skills/deploy-rico/check.sh
Machine-readable JSON output:
bash .claude/skills/deploy-rico/check.sh --json
Exit codes: 0 = all checks passed and Render is current. 1 = stale, unhealthy, or unreachable.
STATUS: ✓ All checks passed — Render is deployed from origin/main and health endpoints are green.
STATUS: ⚠ Render backend is stale — The commit Render is running does not match origin/main. The script prints safe next steps: open the Render dashboard and trigger a manual deploy. Do not redeploy from this script.
STATUS: ⚠ One or more checks did not pass — A health endpoint returned non-200 or no response. Possible causes:
═══════════════════════════════════════════════════
Rico Deployment Verification
2026-06-06 22:49:30 UTC
═══════════════════════════════════════════════════
── Render backend (https://rico-job-automation-api.onrender.com) ──
[ OK ] GET /version → app=ricohunt env=production commit=e3fcfb7 deployed_at=2026-06-06T21:00:00Z
[ OK ] GET /health → HTTP 200 status=ok
── Vercel frontend (https://ricohunt.com) ──
[ OK ] GET /proxy/health → HTTP 200 status=ok
[ OK ] GET / → HTTP 200
── Commit comparison ──
[ INFO ] origin/main → e3fcfb7
[ INFO ] Render deployed → e3fcfb7
[ OK ] Render is up to date with origin/main (e3fcfb7)
═══════════════════════════════════════════════════
STATUS: ✓ All checks passed
═══════════════════════════════════════════════════
/version commit field is "unknown" when Render deployed without a COMMIT_SHA env var set. This is a Render config issue, not a code issue. The health check is still valid./proxy/health returns 403 or 404 when the Vercel project env NEXT_PUBLIC_RICO_API is not set or the proxy rewrite is misconfigured. Check apps/web/next.config.js and Vercel project settings.This skill is read-only. It will never:
git push, git merge, or any write operation.DATABASE_URL, JWT_SECRET, or any secret env var./tmp.To deploy: push to main and use the Render dashboard or Render CLI. Get approval first.