loops!
BrowseSign in
Back to loops
CI
interval
CodexCursor

PR Watch Loop

Poll open PRs labeled codex-watch every 15 minutes, review activity, and flag regressions or stale threads.

1 copies · 28 views

by loops!

Use loop copies the kickoff. Share copies the loop link. Open in Cursor / Claude Code only pre-fill that prompt — they do not install hook files. Download loop saves a README and kickoff into .cursor/loops/pr-watch-loop/ — no hooks required. Full install guide

Sign in to save
Guardrails
Hardened
Anti-gaming rules
Rules the agent must follow so it cannot cheat the exit condition.
  • Do not modify the check command or exit criteria to force success
  • Do not skip, disable, or bypass checks to pass the exit condition
  • If stuck after several iterations, stop and report blockers instead of gaming metrics
How to run this loop
Prompt only
Run “PR Watch Loop” in your agent
Deeplinks and “Open in Cursor” only paste the kickoff prompt. They do not install hook files — your agent cannot tell whether files are on disk until you add them yourself.

Two separate pieces

  • Kickoff prompt — tells the agent the goal, check command, exit condition, and how to self-pace between passes.
  1. 1

    Copy or open the kickoff prompt

    Click Use loop to copy the kickoff into your clipboard. Open in Cursor and Open in Claude Code only open the agent with that prompt — they do not configure automation for you.

  2. 2

    Paste into your coding agent

    Start a chat in Cursor, Claude Code, Codex, or any agent. Paste the kickoff. The prompt includes the goal, iteration limit, shell check, and first step.

  3. 3

    Agent self-paces until done

    The agent runs the loop: act → run check command → read output → repeat until the exit condition is met or max iterations is reached. No install step is required for prompt-only loops.

Full guide with Cursor /loop notes: How to install loops

interval trigger
CI
Every 15m
List watched PRs
Check CI and reviews
Report or act
Watch report delivered for all codex-watch PRs
Rendering diagram…
Steps
What the agent does on each pass.

1. List watched PRs

List open PRs with the codex-watch label. Summarize CI status, review state, and last activity.

gh pr list --label codex-watch --json number,title,state,statusCheckRollup

2. Check CI and reviews

For each watched PR, check failing checks, unresolved review comments, and merge conflicts.

3. Report or act

Post a brief status update. Fix trivial CI failures or ping the author for blockers.

Kickoff prompt
Copy this into your coding agent to start the loop.
/loop 15m Start the "PR Watch Loop".

Goal: keep codex-watch PRs healthy and unblocked.
Between iterations run: gh pr list --label codex-watch --json number,title,state,statusCheckRollup
Exit when: status report is delivered for every watched PR.

Step 1: List codex-watch PRs, check CI and reviews, and report or fix trivial blockers.

Related loops

CI
manual
155 copies
Implement on a branch, run tests, push, open a PR, wait for CI, and loop until checks pass and the PR is ready to merge.

Start the "Ship PR Until Green" loop. Goal: PR is open with all CI checks passing Max iterations: 10 Between iterations run: gh pr checks Exit when: all PR checks are success Step 1: Implement the change, test locally, push, open PR, and fix CI until green. Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.

Claude CodeCursorCodex
pr
ci
ship
continuous-claude
by loops!
View
CI
interval
40 copies
Every 15 minutes, inspect open PRs with a watch label: nudge reviewers, fix CI, rebase if behind main.

/loop 15m Start the "PR Babysitter" loop. Goal: open PRs labeled codex-watch are healthy (CI green, rebased, not stale). Max iterations: 20. Between iterations run: gh pr list --label "codex-watch" Exit when: each watched PR is green and current, or escalated. Step 1: List watched PRs. Fix CI once, rebase if behind, comment if stale. Escalate repeated failures.

CodexCursor
pr
github
ci
boris-cherny
by loops!
View
Testing
manual
Hardened
32 copies
Run the production build, fix compile and bundling errors, and loop until the build succeeds.

Start the "Build Until Green" loop. Goal: production build succeeds Max iterations: 10 Between iterations run: npm run build Exit when: npm run build exits 0 Step 1: Run the build. If it fails, fix the first error, then repeat until green. Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.

CursorClaude Code
build
compile
ci
by loops!
View