Use cases
Use cases
Illustrative setups. The repositories, numbers and names are examples, not customers.
A first pass before a human review
Watch the repos your team works in, so each new PR has a review waiting.
Sample items
- Watched repos: an example web app and its API
- MCP provider: claude
- People read the Verdict and Issues before opening the diff
A repo that learns its own rules
Let developer replies decide what the next review should say.
Sample items
- Approve or reject written replies in the signal approval queue
- Repo context rebuilt from approved learning signals
- Directives from lessons learned added to the repo’s CLAUDE.md
Clearing out quiet PRs
Find open PRs with no activity for a week and decide what to do with each.
Sample items
- Start a stale review batch from the dashboard
- Read each recommendation, such as SAFE_TO_MERGE or NUDGE_AUTHOR
Release triage
Know whether a failed release run is a regression or known noise.
Sample items
- A release monitor on an example Classic Release definition
- Known flaky areas declared in the repo’s context file
- Failure cards posted to a Teams channel
Your repos, your servers, your AI back end
Run PR Bot with Docker Compose or as a macOS desktop app. Reviews go through the MCP provider you configure.