Deploy Verification Loop

On an interval, hit health and smoke endpoints after a deploy until all checks return healthy responses.

0 views•0 uses•by solo lemon.

// parameters

Triggerinterval

Max iterations8

Check commandcurl -fsS https://your-app.example/health

Exit conditionAll configured health endpoints return success

// run_this_loop

Copy the kickoff into your agent first. The blueprint below explains how the loop evaluates progress and when it should stop.

Open in Cursor Open in Claude

Use loop copies the kickoff prompt. Share copies the loop link. Open in Cursor / Claude only pre-fill that prompt — they do not install hook files. Download loop saves the loop as deploy-verification-loop.md.

/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.

// blueprint

The loop contract: target outcome, execution sequence, checks, stopping condition, and safety constraints.

Goal

all post-deploy health and smoke endpoints return success.

// loop_sequence

// loop_sequence_diagram.json

closed loop

Trigger

interval event

Actions block

3 steps

1Check health endpoints

2Investigate failures

3Re-verify

Feedback gate

Evaluate: curl -fsS https://your-app.example/health

Run the check, read the output, then decide whether the loop is complete.

Check failed

Repeat actions with the latest feedback.

Success

All configured health endpoints return success

Safety capMax 8 iterations

// steps

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.