pr-watch - an event-driven PR inbox for AI teams

In a fast AI startup workflow, I use it to stay on top of PRs without losing deep focus.

pr-watch - an event-driven PR inbox for AI teams

I recently added a new AI agent command called pr-watch to my command collection.

TL;DR

I use pr-watch to stay on top of PRs across repos without constant tab-checking or noisy AI polling. It only wakes the assistant when something meaningful changes, so I can keep deep focus and still respond quickly when reviews or CI need action.

The core idea is simple: keep a live PR inbox across repositories, but only wake up the assistant when there is meaningful change (review activity, CI status changes, merge state updates).

Why I built it

I am currently working with an international team on an AI-driven startup, and we use Claude Code heavily in day-to-day development.

As development pace grows, so does PR volume across multiple repos and apps. In that setting, pull requests create constant background stress:

  • "Did someone request changes?"
  • "Did CI just fail?"
  • "Is there a PR waiting on me to review?"
  • Without a good system, I either keep context-switching to GitHub tabs or check too late.

    I still want to do thoughtful reviews myself, but now with AI support: I use AI to help review, filter, and steer findings so signal stays high and action stays clear.

    What makes pr-watch different

    Most AI-powered monitoring loops are expensive in both attention and tokens.

    pr-watch avoids that by splitting responsibilities:

  • A lightweight Node.js poller keeps watching GitHub in the background.
  • The assistant sleeps while nothing changes.
  • The assistant only wakes up to render an update when an event occurs.
  • That means no constant "nothing changed" chatter and no token burn for idle polling.

    How it helps in practice

    In daily use, it gives me one clear PR inbox that shows:

  • where the ball is (my turn vs their turn),
  • grouped PRs per repository,
  • waiting time with staleness warnings,
  • and a next action (/review-pr or /review-comments).
  • This workflow also improves my own understanding of the codebases we are building, because I stay continuously involved in review loops across all repos and apps.

    So in a high-velocity startup setting, pr-watch helps me stay focused longer, review better, and still react fast when collaboration actually needs me.

    Links

    Back to all notes