验证部署
- 作者仓库星标 0
- 作者仓库 skills-registry
- 领域
- 运维部署
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tomevault-io · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 命令执行
- 网络行为
- 允许外网请求
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
步骤 1:阅读 DEPLOYMENTDOCS/DEPLOYEDENV.md
摘录:`FRONTEND_URL`、`BACKEND_URL`以及任何其他服务 URL。如果该文件不存在:“未找到 DEPLOYED_ENV.md。请手动提供已部署的服务 URL,或先运行部署项目。”将值加载到 shell 变量中以供下面的检查使用。
步骤 2:所有服务的 HTTP 健康检查
跟踪步骤 5 中汇总表的每项检查是否通过。
第 3 步:代理浏览器对前端进行目视检查
获取快照后,检查 HTML 中是否有错误指示符: 如果快照包含以下任意一项: `"Error"`、`"404"`、`"Cannot GET"`、`"Application error"`、`"Something went wrong"` → 将前端视觉检查标记为“失败” 如果快照显示正常的 UI 元素(导航、内容、按钮、表单)→ 标记为“通过”
第5步:打印汇总表
填写步骤 2-4 中的实际 URL 和实际通过/失败结果。对于任何未通过的检查,请使用`✗ FAIL`。
第 6 步:失败时
如果任何检查失败:清晰打印:`"VERIFICATION FAILED: [service name] is not responding"` 根据失败的服务建议具体修复:前端失败:“检查 Vercel/Netlify 仪表板是否存在构建错误”后端失败:“检查渲染仪表板以了解部署状态 - 免费套餐可能仍处于冷启动状态(最多 30 秒)”
# verify-deployment
Confirms all deployed services are live, reachable, and communicating correctly. Produces a pass/fail summary table and a frontend screenshot.
---
## Step 1: Read DEPLOYMENT_DOCS/DEPLOYED_ENV.md
Extract: `FRONTEND_URL`, `BACKEND_URL`, and any other service URLs.
If the file doesn't exist:
> "No DEPLOYED_ENV.md found. Please provide your deployed service URLs manually, or run deploy-project first."
Load the values into shell variables for use in the checks below.
---
## Step 2: HTTP health checks for all services
```bash
check_url() {
local name=$1 url=$2 max_retries=${3:-1}
for i in $(seq 1 $max_retries); do
STATUS=$(curl -s -o /dev/null -w "%{http_code}" --max-time 30 "$url" 2>/dev/null || echo "000")
if [ "$STATUS" -ge 200 ] && [ "$STATUS" -lt 400 ]; then
echo "✓ $name → HTTP $STATUS"
return 0
fi
if [ $i -lt $max_retries ]; then
echo " $name: HTTP $STATUS, retrying in 30s (attempt $i/$max_retries)..."
sleep 30
fi
done
echo "✗ $name → HTTP $STATUS (FAILED)"
return 1
}
# Frontend (2 attempts — no cold start)
check_url "Frontend" "$FRONTEND_URL" 2
# Backend health endpoint (3 attempts — Render free tier cold start ~30s)
check_url "Backend /health" "$BACKEND_URL/health" 3
```
Track whether each check passed or failed for the summary table in Step 5.
---
## Step 3: agent-browser visual check of frontend
```bash
agent-browser open "$FRONTEND_URL"
agent-browser wait --load networkidle
agent-browser screenshot DEPLOYMENT_DOCS/verify-frontend.png
agent-browser snapshot -i
```
After getting the snapshot, inspect the HTML for error indicators:
- If snapshot contains any of: `"Error"`, `"404"`, `"Cannot GET"`, `"Application error"`, `"Something went wrong"` → mark frontend visual check as **FAILED**
- If snapshot shows normal UI elements (nav, content, buttons, forms) → mark as **PASSED**
```bash
agent-browser close
```
---
## Step 4: Cross-service connectivity test
```bash
# Test backend API health endpoint that also checks DB connectivity
API_RESPONSE=$(curl -s --max-time 30 "$BACKEND_URL/api/health" 2>/dev/null)
if echo "$API_RESPONSE" | python3 -c "import sys,json; d=json.load(sys.stdin); assert d.get('status') in ['ok','healthy','up'], f'unexpected: {d}'" 2>/dev/null; then
echo "✓ Backend API responding correctly"
else
echo "ℹ Backend /api/health returned: $API_RESPONSE"
echo " (This is OK if your backend doesn't have a /api/health endpoint)"
fi
# Test DB connectivity via backend (if backend exposes it)
DB_RESPONSE=$(curl -s --max-time 30 "$BACKEND_URL/api/health/db" 2>/dev/null)
if [ -n "$DB_RESPONSE" ]; then
if echo "$DB_RESPONSE" | python3 -c "import sys,json; d=json.load(sys.stdin); assert d.get('db') in ['connected','ok','healthy']" 2>/dev/null; then
echo "✓ Database connection verified via backend"
else
echo "ℹ DB health response: $DB_RESPONSE"
fi
else
echo "ℹ No /api/health/db endpoint — skipping DB connectivity check"
fi
```
---
## Step 5: Print summary table
```
=== Deployment Verification Summary ===
Service Status URL
─────────────────────────────────────
Frontend ✓ PASS <FRONTEND_URL>
Backend ✓ PASS <BACKEND_URL>
Backend API ✓ PASS /api/health
Database ✓ PASS via backend
Screenshot saved: DEPLOYMENT_DOCS/verify-frontend.png
═══════════════════════════════════════
```
Fill in actual URLs and actual pass/fail results from Steps 2–4. Use `✗ FAIL` for any check that did not pass.
---
## Step 6: On failure
If any check FAILS:
1. Print clearly: `"VERIFICATION FAILED: [service name] is not responding"`
2. Suggest a specific fix based on which service failed:
- **Frontend fails:** "Check Vercel/Netlify dashboard for build errors"
- **Backend fails:** "Check Render dashboard for deploy status — free tier may still be cold-starting (up to 30s)"
- **DB fails:** "Check Supabase/Neon dashboard — project may have paused"
3. Ask the user: `"Would you like me to re-run verification after you've checked? (yes/no)"`
4. **Do NOT claim the deployment is successful if any check fails.**
---
> Source: [AayushMS/deploy-skills](https://github.com/AayushMS/deploy-skills) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
章节与文件索引
按说明文件中的顺序排列。
步骤 1:阅读 DEPLOYMENTDOCS/DEPLOYEDENV.md
步骤 2:所有服务的 HTTP 健康检查
第 3 步:代理浏览器对前端进行目视检查
第5步:打印汇总表
第 6 步:失败时
文件/命令 -> FRONTEND_URL · BACKEND_URL · "Error" · "404" · "Cannot GET" · "Application error" · "Something went wrong" · ✗ FAIL
内容校验值 -> aa2ad633a408
当前原文的自动摘译,尚未人工审校。
步骤 1:阅读 DEPLOYMENTDOCS/DEPLOYEDENV.md
提取:
FRONTEND_URL、BACKEND_URL以及任何其他服务 URL。如果该文件不存在:“未找到 DEPLOYED_ENV.md。请手动提供已部署的服务 URL,或先运行部署项目。”将值加载到 shell 变量中以供下面的检查使用。