loops!Staging Smoke Test
Run a fixed smoke checklist against staging after deploy: auth, core flows, and error budgets.
3 copies · 33 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/staging-smoke-test/ — 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. Run smoke checklist
Execute the staging smoke script or manual checklist (login, critical path, webhooks).
npm run smoke:staging
2. Fix failures
If smoke fails, trace logs, fix the smallest issue, and redeploy or hotfix as appropriate.
3. Confirm green
Re-run smoke until all checklist items pass.
npm run smoke:staging
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.
Related loops
/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.