After running Claude Loops in production for several months, the same five patterns keep paying for themselves. None of them is fancy. They are just things you would otherwise do manually 20 times a week.
1. CI watchdog
Polling a long-running CI build is the single most common loop on our team. You push a branch, walk to coffee, come back to a green check or a useful failure summary.
/loop 3m check the latest GitHub Actions run on my current branch. Only ping me on success, failure, or a flaky retry. Stop after success.
Why this version works: the "only ping me on…" clause eliminates noise; the "stop after success" gives a natural end.
2. PR babysitter
You have an open PR. Reviewers are slow. Comments trickle in. You do not want to refresh GitHub every 10 minutes.
/loop 15m list my open PRs. Report new review comments, requested changes, or merge conflicts since the last check.
Pair this with /schedule for a daily standup digest and you have covered both ends.
3. Error log scout
If you operate any production service, this loop earns its keep on day one.
/loop 5m tail the last 500 lines of logs/app.log. Group new ERROR lines by stack trace fingerprint. Report only fingerprints I have not seen before.
The "fingerprints I have not seen before" framing is the magic. You get told about new patterns, not the same crash 500 times.
4. Deploy babysitter (dynamic mode)
This is the loop that converts the most skeptics. You kick off a deploy, then forget it exists until Claude tells you it is live.
/loop watch the staging deploy. Tell me when each stage starts and finishes. End the loop once production is live.
No interval — Claude picks the pacing. Polls fast during active stages, sleeps long during the queue wait. You save tokens and get faster signal.
5. Morning brief (with /schedule, not /loop)
Technically not a /loop — but worth listing because it solves the same recurring-task problem. /schedule runs in the cloud, so you do not need Claude Code open.
/schedule every weekday at 8:30am: summarize overnight new PRs, failed CI runs, urgent emails, and today's calendar.
By the time you open your laptop, the digest is waiting.
Pattern shared across all five
Every one of these loops has three things in common:
- A clear task. Specific verb, specific scope.
- An "only tell me if…" clause. Filters noise.
- A stop condition. Either explicit ("end when X") or implicit ("until I close the session").
Build all three into every loop you write and you will rarely be unhappy with one.