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
claude-code · codex
Implementation note
Run from a feature branch with gh authenticated. The 10-turn cap keeps a stubborn CI failure from becoming an expensive stalemate.
More git loops
Rebase train conductor
Keep a stack of feature branches rebased in order as their parents merge, resolving trivial conflicts and flagging risky ones for a human.
/loop 15m for each branch listed in .rebase-train (in order), rebase it onto its updated parent, resolve only trivial conflicts (imports, formatting, lockfiles), run the test suite, and push with `--force-with-lease`; if a conflict touches logic, stop that branch and leave a summary comment on its PR instead
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
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.