Babysit PRs to merge-ready
Run a check loop every 5 minutes until your PR is merge-ready, optionally shipping when passing.
Prompt
/loop 5m /pr-babysit check. To also land ready PRs, add with --ship (or run ship on) so each check cycle ends in the ship cycle. Shipping is opt-in. The default still stops at merge-ready
claude-code
Source: rakaarwaky ↗graded C · 50/100 — how grades work (Safety Score v2) →
Similar loops
All git loops →B
/goalGitmedium risk
Ship a PR until green
Implement a change, open the PR with gh, then keep fixing CI failures until every check passes, all in one goal loop.
/goal a PR is open for this change and every CI check passes — implement it, test locally, push, open the PR with `gh pr create`, then keep fixing failures (re-check with `gh pr checks`) until green; stop after 10 turns
C
/loopGitmedium risk
Verify agent output before it ships
Run one agent in an isolated worktree and release its staged output only after a second agent verifies the work.
Use Loop Harness for scheduled repository work such as CI triage, issue grooming, dependency updates, or docs sync. Set [retry limit], then start an isolated git worktree. Let one Claude session stage a patch or outbox message and a second Claude session verify it against explicit criteria. Ship only after a pass; otherwise preserve the findings and retry only within the limit. Finish with the source revision, staged output, verifier result, delivery status, and next run.
C
/goalGitlow risk
Commit message hygiene on a branch
Rewrite the commit messages on your feature branch to conventional-commit format with meaningful bodies before opening the PR, leaving the code untouched.
/goal every commit on this branch (ahead of main) has a conventional-commit subject under 72 characters and a body explaining why — use interactive rebase to reword only (no code changes, no commits dropped), verify with `git log main..HEAD`, and confirm the diff against the original branch tip is empty; stop after 5 turns