Config drift check

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
claude-code · codex · cursor

Implementation note

Compares key names only, never secret values, so nothing sensitive enters the transcript. Catches the classic works-in-staging-missing-in-prod config bug early.

Source: looprepo

More devops loops

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

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

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