Checking CI Every Few Minutes by Hand? Let /loop in Claude Code Watch the Pull Request.

At a glance

• Type /loop with a prompt and Claude Code reruns it while your session stays open.
• Leave out the interval and Claude picks the next wait itself.
• Ask Claude to list or cancel loops, and know they expire after seven days.

You keep typing "did CI pass yet?" after every push. Claude Code can do that for you. The bundled /loop skill reruns a prompt on an interval inside your current session, between your turns.

Why it matters

Polling by hand breaks focus. Anthropic's scheduled tasks docs describe /loop as the quickest way to run a prompt on repeat while the session stays open, for babysitting a pull request or a long build. The loop uses your local files, the tools you already allowed, and the MCP servers the session already has. Hand the recheck to /loop and go back to the next task.

How to let Claude watch a pull request

We built these steps from Anthropic's docs and have not run them in a live session.

1. Start or reopen the Claude Code session on the branch you pushed, and keep it open. Loops fire only while Claude Code is running and idle.
2. For a loop that sets its own pace, type /loop and a prompt with no interval. After each pass, Claude picks a wait between one minute and one hour and prints the wait and the reason.
3. For a fixed schedule, put an interval first, such as 10m. Supported units are s, m, h, and d. Seconds round up to a whole minute, and Claude says when it rounds.
4. Ask "what scheduled tasks do I have?" to see each task's ID, schedule, prompt, and next run time.
5. Stop it the right way. A self paced loop stops when you press Esc while it waits. A fixed interval loop ignores Esc and Ctrl+C, so ask Claude to cancel it by name.
6. For a one time nudge, skip /loop and ask in plain words, such as "in 45 minutes, check whether the integration tests passed".

# We have not run this script end to end on every platform. Type each line into a Claude Code session, one at a time.

/loop check whether CI passed on this branch's pull request and address any new review comments

/loop 10m check whether CI passed on this branch's pull request and tell me what changed

what scheduled tasks do I have?

cancel the CI check loop

in 45 minutes, check whether the integration tests passed

If you run the same check in every session, put the instructions in .claude/loop.md in the project, or ~/.claude/loop.md for all projects. A bare /loop then uses that file, and edits take effect on the next pass.

Gotchas

• Closing the terminal stops it. Loops live in the session. For checks that must run with the laptop shut, the docs point to cloud scheduled tasks, Desktop scheduled tasks, or GitHub Actions.
• Seven days, then gone. A recurring task fires one last time and deletes itself seven days after you create it.
• Runs land a little late. Claude Code spreads runs out so sessions do not all call at once.
• Resume restarts only some loops. claude --resume restores fixed interval tasks that have not expired, but a self paced /loop does not come back.

Sources:

• Run prompts on a schedule, Claude Code docs

Recommended AI prompt

Copy this paragraph into ChatGPT, Claude, Gemini, Grok, or whatever AI you use.