loops!Deploy Verification Loop
On an interval, hit health and smoke endpoints after a deploy until all checks return healthy responses.
3 copies · 39 views
by loops!
Use loop copies the kickoff. Share copies the loop link. Open in Cursor / Claude Code only pre-fill that prompt — they do not install hook files. Download loop saves a README and kickoff into .cursor/loops/deploy-verification-loop/ — no hooks required. Full install guide
- Do not modify the check command or exit criteria to force success
- Do not skip, disable, or bypass checks to pass the exit condition
- If stuck after several iterations, stop and report blockers instead of gaming metrics
Two separate pieces
- Kickoff prompt — tells the agent the goal, check command, exit condition, and how to self-pace between passes.
- 1
Copy or open the kickoff prompt
Click Use loop to copy the kickoff into your clipboard. Open in Cursor and Open in Claude Code only open the agent with that prompt — they do not configure automation for you.
- 2
Paste into your coding agent
Start a chat in Cursor, Claude Code, Codex, or any agent. Paste the kickoff. The prompt includes the goal, iteration limit, shell check, and first step.
- 3
Agent self-paces until done
The agent runs the loop: act → run check command → read output → repeat until the exit condition is met or max iterations is reached. No install step is required for prompt-only loops.
Full guide with Cursor /loop notes: How to install loops
1. Check health endpoints
Curl configured health/smoke URLs. Record status codes and response bodies.
curl -fsS https://your-app.example/health
2. Investigate failures
If any endpoint fails, check recent deploy logs, env vars, and migrations. Apply the smallest fix.
3. Re-verify
Re-run health checks after fixes or rollback decision.
/loop 15m Start the "Deploy Verification Loop". Goal: all post-deploy health and smoke endpoints return success. Max iterations: 8. Between iterations run: curl -fsS <your-health-url> Exit when: every configured endpoint succeeds. Step 1: Hit health/smoke URLs. If any fail, inspect deploy logs and fix or escalate.
Related loops
Start the "Staging Smoke Test" loop. Goal: staging smoke checklist passes Max iterations: 6 Between iterations run: npm run smoke:staging Exit when: smoke command exits 0 Step 1: Run the staging smoke checklist. Fix the first failing item, then repeat. Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.
/loop 5m Start the "CI Failure Watcher" loop. Goal: latest CI run on this branch is green. Max iterations: 12. Between iterations run: gh run list --branch $(git branch --show-current) --limit 1 Exit when: latest run conclusion is success. Step 1: Check CI status. If failed, read logs, fix root cause, verify locally, and push if needed.