Every new pull request
Every pull request waits for my first pass, and most of what I flag, a careful second reader would have caught.
How it goes now
New pull request.Open it.Read the description.Scroll the diff.Missing test.Comment.Unchecked error.Comment.Back to what I was doing.
Every pull request, before anyone else looks.
Tell Kitewell once
When a pull request is opened in my repo, have my Codex agent review it, have my Claude Code agent check that review against the code, and post the checked review on the pull request once I approve.
That's the whole setup. Kitewell lays out every step for you to check, and nothing is saved until you apply it.
Then it runs on its own
Review of #482Running on this computer
- Review the pull requestCodex reads it with gh and lists bugs, missing tests, and risky changes, each with its file and line.Done
- Check the reviewClaude Code checks each finding against the diff, drops the wrong ones, and adds what was missed.Done
- Wait for your OKRead the checked review, then approve, send it back with a note, or reject.Waits for you
- Post it on the pull requestgh pr review --comment, as your own GitHub account.Done
What you get instead
Review of #482
Waiting for you: post the checked review on the pull request?
Check the review
- #482 Move sessions to the new store
- Confirmed: logout.ts still reads the old session key, line 41.
- Confirmed: no test covers an expired session.
- Dropped: a missing null check Codex flagged; the caller already checks.
Post the checked review on the pull request?
Good to know
- GitHub starts each run through Kitewell's relay, with no port open on your computer. Set the webhook to take only pull_request.opened, and have Kitewell check GitHub's signature.
- Both agents run gh to read the pull request, which takes network access and permission to run commands: allow it in each tool's own settings, or turn on Bypass permission prompts on its entry in Agents & models. They read code someone else wrote, so use this where you know who opens pull requests.
- On Windows, a pull request event larger than about 30,000 characters may not start a run yet.
What it needs
- A command-line agent such as Codex or Claude Code, installed and signed in
- A Git repository and the gh command
- Kitewell Personal or Team, signed in to Dagu Cloud, for the GitHub webhook
More chores
- Every morningEvery morning I open each pull request just to work out which one could break something.
- Every new issueEvery new issue arrives without a label, and half the bug reports don't say how to reproduce the problem.
- Every weekday at 2:00Some mornings the tests on main are red, and my first hour goes to finding out why and fixing it.