KitewellRelease status
← All chores

Every morning

Every morning I open each pull request just to work out which one could break something.

How it goes now

Open the PR list.Open one.Scroll the diff.What does this touch?Open the next.Lose track of the first.Start over.

Every morning, before review even starts.

Tell Kitewell once

You
Every weekday at 9:00, have my Claude Code agent list the open pull requests in this repo with gh, review each diff, and write a Markdown digest ordered by risk. Save it under reviews/ with today's date.

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

PR digestRunning on this computer

  1. Review the open pull requestsLists them with gh, reads each diff, and writes three lines per PR, riskiest first.Done
  2. Save the digestWritten to reviews/<date>.md and shown in the run.Done

What you get instead

reviews/2026-10-06.md

#482 Move sessions to the new store

Changes: how sessions are read and written.

Could break: anyone signed in during the deploy.

Ready: not yet. It needs a migration note.

#479 Fix the date picker in Safari

Changes: one component.

Could break: little.

Ready: yes.

Sample data

Good to know

  • The agent runs in your checkout and uses gh, so private repositories need no extra credential.
  • On Personal or Team, an alert can send the digest to your email or Slack when the run finishes.
  • Your computer needs to be on and awake when it runs. A run missed while it slept starts when it wakes, within 24 hours by default.

What it needs

  • A command-line agent such as Codex or Claude Code, installed and signed in
  • A Git repository and the gh command

More chores