reviewGOOSE¶
PRs that merge in minutes, not days.
The Problem¶
Industry average PR merge time is 4.5 days. Most of that is waiting—unclear whose turn it is, missed notifications, context switching.
The Solution¶
reviewGOOSE tracks whose turn it is and notifies the right person at the right time.
How It Works¶
graph LR
A[GitHub PR Event] --> B[reviewGOOSE]
B --> C{Turn Detection}
C -->|Author needs to act| D[Notify Author]
C -->|Reviewers need to act| E[Notify Reviewers]
C -->|Ready to merge| F[Notify Author]
D --> G[Slack/Discord/Desktop]
E --> G
F --> G
B --> H[Dashboard Update]
- GitHub App monitors your PRs
- Turn detection determines who needs to act: fix tests, review, address feedback, merge
- Smart notifications via Slack DM, channel post, or desktop app
- Dashboard shows PRs organized by "waiting on you" vs "waiting on others"
Turn Detection Logic¶
reviewGOOSE determines whose turn it is by analyzing:
- CI status: Are tests passing or failing?
- Review state: Approved, changes requested, or pending?
- PR state: Draft, ready for review, or approved?
- Merge status: Mergeable or blocked?
graph TD
Start[New PR Event] --> Draft{Is Draft?}
Draft -->|Yes| WaitAuthor[Wait for Author]
Draft -->|No| Tests{Tests Passing?}
Tests -->|Failing| WaitAuthor
Tests -->|Passing| Reviews{Has Reviews?}
Reviews -->|No| WaitReviewer[Wait for Reviewer]
Reviews -->|Yes| Approved{All Approved?}
Approved -->|No| Changes{Changes Requested?}
Changes -->|Yes| WaitAuthor
Changes -->|No| WaitReviewer
Approved -->|Yes| Mergeable{Can Merge?}
Mergeable -->|Yes| ReadyMerge[Ready to Merge]
Mergeable -->|No| WaitAuthor
Components¶
| Component | What it does |
|---|---|
| GitHub | Connects to your repos |
| Web | Dashboard at <org>.reviewgoose.dev |
| Slack | Channel posts and DMs |
| Discord | Channel posts and DMs (Preview) |
| Desktop | Native notifications with sounds |
| CLI | Terminal view for developers who live in the shell |
Pricing¶
Free for public repos. See Plans for private repos.
Questions? Get Support