For engineering managers
See where the work waits, and who it waits on.
See where pull requests wait, who they wait on, who carries the reviews and how AI-written code compares. Everyone knows what to pick up next.
Sign in with GitHub, then pick your org. No card.
Insights
One sentence on how reviews are going.
The page opens with how soon reviews start and how that moved since the previous period. Four numbers follow, each with its trend. Worth a look names the bottleneck, the longest wait, the slowest and fastest merges and the fastest reviewer, with the people behind them.
- Time to first review and time to merge, week by week
- Stale open PRs and merges with no review
- Who the open work waits on, with their load
People
Who keeps the team going, and who goes quiet.
Six signals look at the days you pick and name up to three people each. Every person has a row with what they reviewed, merged and opened, how big their pull requests run and how each moved since the previous period.
- Reviewed, merged and opened, per person
- Median pull request size
- Rubber stamps out of approvals
Reviewers
Who the open work waits on.
One load bar per reviewer, split by how long each request has waited: under a day, one to five days, over five days. The opening sentence says what share sits with the busiest reviewer.
- Oldest wait per reviewer
- Requests answered and turnaround for the range
AI
How AI-written code compares.
An agent roster shows what Claude, Codex, Copilot, Cursor, Devin and others wrote, and how it fared. AI-written and human pull requests sit side by side on five measures.
- Time to first review
- Review rounds
- Cycle time
- Merge rate
- Size
Queue
Every open pull request, and who it waits on.
One row per open PR, longest wait first. Each row says who it waits on and since when, and flags stale PRs, unresolved threads, change requests, drafts and AI-written PRs.
- Filter to waiting, stale or drafts
- Narrow by repository, author or reviewer
Six signals about the people on your team.
Each one reads the range you pick, 7, 30 or 90 days, and names up to three people. Bots never appear.
Keeping the team going
Reviewed the most pull requests, with their share of all reviews.
Slow or silent
Had five or more review requests due and either answered under half or took over two days at the median.
Opens but never reviews
Opened three or more pull requests and reviewed none.
Big PRs, hard to review
The largest median size, 400 lines or more, among people who opened three or more.
Small PRs, easy to review
The smallest median size, 100 lines or less, among people who opened three or more.
Rubber stamps
Five or more approvals, most of them with no review notes on PRs of 20 lines or more.
Built to unblock each other, not to score people.
GitHub only
Stett reads GitHub and nothing else.
No score for a person
There is no single score for a person. Each signal shows its rule.
Yours to see
Your own numbers, never a colleague's.
Five or no median
Medians need at least five other people.
People, not bots
Bots and review apps never count as people.
What waits on you, and your own numbers.
My work lists the pull requests you wrote or were asked to review by name. Me shows your review counts, wait times and pull request sizes beside the team median.
Me shows no other person's name or figures. Team medians leave you out and appear only when at least five other people have data. Members can also open AI to see how AI-written pull requests compare.
Priced per seat, on your org.
Team is $19 per seat a month, or $15 per seat a month billed yearly. The 14-day trial starts when you install the GitHub App and covers up to 25 people. No card. You pay for people who sign in, up to a seat ceiling you set.
Not an org admin? Send them this.
Only an org owner can install the GitHub App. Copy this note, or open it in your email.
Subject: Can you install Stett on our GitHub org?
I'd like to try Stett on our org for 14 days. It shows where our pull requests wait and gives each of us a guided review. It needs an org owner to install its GitHub App. Six of its eight permissions are read only. The two that write act only when one of us starts something. Everything it asks for and keeps is here: https://www.stett.dev/for-admins. No card for the trial.
Unblock your team's pull requests.
Install the GitHub App on your org and Team is free for 14 days. No card.