Deploy-poll loop

A hands-free ops loop that polls your deploy every two minutes, runs the smoke test the moment it goes live, and stops with a report if any check fails.

prompt
→ Claude Code
/loop every 2 minutes: check deploy status; when it's live, run the smoke test and summarize; if smoke test fails, report the failing check and stop Guardrails: Stop when the goal is verifiably met, or stop after 15 iterations, whichever comes first. Keep changes minimal and never touch files outside the task’s scope.
claude-code

Implementation note

When to use: you have kicked off a deploy and the next twenty minutes are otherwise dead time — waiting to see it go live, then remembering to run the smoke test against it. How it works: every two minutes the loop checks deploy status. The moment the deploy is live it runs the smoke test and summarizes the results; if the smoke test fails, it reports the failing check and stops rather than continuing to poll or attempting fixes. Safety: the stop-on-failure clause is the notable rail — a failed smoke test halts the loop with a report, leaving the response decision (rollback, hotfix, investigate) to you instead of the loop improvising remediation against production. Everything it does is read-and-report: status checks and test runs, no code or infrastructure changes. It is cheap at a two-minute cadence, but kill it once the deploy is confirmed rather than leaving it polling. Hardened 2026-07-27: explicit stop/cap/verification guardrails appended; regraded D→A.

Source: Claude Directory blog ↗graded A · 95/100 — how grades work →

More devops loops

Ship infrastructure readiness gates

Loop/goalGitHubB

Shape and execute infrastructure readiness objectives by gathering evidence, seeking approval at decision boundaries, then validating provisioning, configuration, and rollback in non-production before production deployment.

prompt
→ Claude Code
/goal Use the installed shape-goal and goal-engine skills to discover, approve, and complete this repository's next Infrastructure / Deployment Readiness objective. During shaping, load shape-goal's required-input specification for Infrastructure / Deployment Readiness; exhaustively inspect repository instructions, Git state and history, infrastructure-as-code, environment and secret references, build artifacts, deployment workflows, health checks, runbooks, rollback paths, supported environments, prior incidents and goals, the project harness, and connected authoritative systems before asking the user. Resolve every material input from evidence where possible. Continue inside this /goal only when an already-approved Goal Contract or authoritative artifact resolves every owner decision. Otherwise create or resume SHAPING.md, save the unresolved decision and one recommended question, stop as Approval required, and tell the user to resume shape-goal outside /goal; do not ask the question or take another autonomous turn, and do not make production changes before approval. Then hand off within this same goal to goal-engine to reconcile infrastructure and application assumptions, validate provisioning and configuration in approved non-production or simulated environments, verify artifact provenance, migrations, smoke and health gates, observability, failure handling, and rollback, and remove verified readiness blockers; apply relevant assurance overlays, repository-native verification, regression protection, independent review where warranted, durable progress state, and reusable closeout. Do not declare success when shaping is complete. Finish only when every approved readiness gate passes with surfaced evidence, environment differences and residual risks are documented, rollback remains viable, and no production deployment or mutation has occurred without explicit authority. Stop only for a contract-defined blocker, approval boundary, budget, material goal drift, or two consecutive no-progress cycles

Next.js 15 app deploys to a Vercel preview…

Loop/goalGitHubA

Community goal loop for devops, sourced from github. Verified exit condition, evaluator-gated.

prompt
→ Claude Code
/goal Next.js 15 app deploys to a Vercel preview URL returning 200, with brand tokens (colors + Plus Jakarta Sans/Inter/IBM Plex Mono) configured and Supabase magic-link auth gating /dashboard so logged-out users redirect to /login; you prove this by npm run build passing, the preview URL, and an incognito visit to /dashboard redirecting; do not add features beyond auth shell, do not change the locked stack; or stop after 100 turns