Add pull request health loop workflow#25
Conversation
📝 WalkthroughWalkthroughREADME.md adds a “Keep a Pull Request Green” entry under “Git and PR Automation,” describing PR health checks, bounded repair attempts, a blocking stop evaluator, and human merge approval. ChangesPR workflow documentation
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Line 95: Update the README entry for “Keep a Pull Request Green” to link
directly to the source site's “Ship PR Until Green” pull-request workflow, or
rename the entry so its title and description accurately match the existing
“Build Your First Agent Loop” destination.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| - [Superpowers git worktrees](https://github.com/obra/superpowers) - Run parallel workstreams using git worktrees — each agent works in its own isolated copy of the repo. | ||
| - [gstack ship pipeline](https://github.com/garrytan/gstack) - Full deploy pipeline: merge PR → deploy → post-deploy monitoring loop. Chains `/ship` → `/land-and-deploy` → `/canary` skills. | ||
| - [Autoresearch branch-per-run](https://github.com/karpathy/autoresearch) - Creates a new git branch for each autonomous experiment run, tracks results in `results.tsv`, keeps or discards based on evaluation. | ||
| - [Keep a Pull Request Green](https://loopengineering.pro/blog/build-your-first-agent-loop) - Keeps one pull request healthy with a project loop prompt, scheduled `/loop` checks, a blocking `Stop` hook evaluator, bounded repair attempts, and a human merge decision. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Link to the PR-specific workflow
The linked page is a general “Build Your First Agent Loop” checklist, not the documented pull-request workflow. The source site separately lists “Ship PR Until Green” with PR checks and a merge-ready exit condition. Please link directly to that workflow or rename the entry to match the destination. (loopengineering.pro)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.md` at line 95, Update the README entry for “Keep a Pull Request
Green” to link directly to the source site's “Ship PR Until Green” pull-request
workflow, or rename the entry so its title and description accurately match the
existing “Build Your First Agent Loop” destination.
Adds one reproducible workflow to Git and PR Automation.
It combines a repository loop prompt, Claude Code's scheduled /loop\ command, and a blocking \Stop\ hook that evaluates local tests plus GitHub PR checks. The recipe includes prerequisites, copyable configuration, acceptance evidence, repair limits, and a human merge boundary.
Summary by CodeRabbit