verify deployment

DevOps Community

Skill notes

Step 1: Read DEPLOYMENTDOCS/DEPLOYEDENV.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

Track whether each check passed or failed for the summary table in Step 5.

Step 3: agent-browser visual check of frontend

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

Step 5: Print summary table

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: Print clearly: "VERIFICATION FAILED: [service name] is not responding" 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)"

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
DevOps
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Read DEPLOYMENTDOCS/DEPLOYEDENV.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.

02
Step 2: HTTP health checks for all services

Track whether each check passed or failed for the summary table in Step 5.

03
Step 3: agent-browser visual check of frontend

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

04
Step 4: Cross-service connectivity test

Step 4: Cross-service connectivity test

05
Step 5: Print summary table

Fill in actual URLs and actual pass/fail results from Steps 2–4. Use `✗ FAIL` for any check that did not pass.

06
Step 6: On failure

If any check FAILS: Print clearly: `"VERIFICATION FAILED: [service name] is not responding"` 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)"

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.