devops loops

7 loops in this category.

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
/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
devopsmedium risk

Check whether the deploy finished and summarize what changed

/loopnew

A 5-minute watch loop that polls whether a deploy has finished and, once it lands, summarizes what changed. It is a read-only status watcher rather than an agent driving toward a finish condition.

prompt
→ Claude
/loop 5m check whether the deploy finished and summarize what changed
devopshigh risk

Docker image slimming

/goalloopreponew

Iteratively shrink a Docker image under a size target using multi-stage builds, smaller base images, and layer cleanup, verifying the container still boots each turn.

prompt
→ Claude
/goal `docker images` shows the app image under 300 MB — apply one slimming change per turn (multi-stage build, slimmer base image, prune build deps, consolidate layers), rebuild, and verify the container starts and passes its healthcheck before the next change; stop at the target or after 8 turns
devopslow risk

Capture a post-release baseline

Run the standard benchmarks against a finished release and record a reproducible baseline for future comparison.

prompt
→ Claude
After current releases finish, run the standard benchmarks and record the results as the new baseline.
devopshigh risk

Config drift check

/looploopreponew

Compare environment config files and example templates every hour and report keys that exist in one environment but not the others.

prompt
→ Claude
/loop 60m diff the keys (not values) across .env.example, config/staging.yaml, and config/production.yaml; report any key present in one file but missing in another, and any key in .env.example that no code references anymore
devopslow risk

Batch a release without the stale work

Exclude unfinished or stale branches, combine the valid changes, and ship a complete artifact from the latest integrated main.

prompt
→ Claude
Review pending changes and pull requests, exclude stale or unfinished work, combine the valid changes, and release them together.
devopshigh risk

Ship one customer AI priority

Advance a single customer priority into a validated, gradually released system with monitoring, approvals, and outcome evidence.

prompt
→ Claude
Run this when a customer requests an AI workflow, reports a failure, or reaches an operations review. Choose one priority, such as enriching leads, drafting emails, summarizing meetings, or updating a CRM. Define the owner, inputs, approvals, success metric, and ROI hypothesis. Dry-run it on realistic customer data, fix the smallest verified problem, then release through approved stages and monitor production. Finish with the outcome, evidence, customer update, lessons saved, and next review.
devopshigh risk