I was spending 2 hours a day triaging GitHub PRs — so I built an AI extension to fix it

The problem I review a lot of pull requests. Not because I'm a reviewer by trade, but...

martedì 23 giugno 2026 New tab

427 words~2 min read

The problem

I review a lot of pull requests. Not because I'm a reviewer by trade, but because I'm a solo developer running a few Chrome extensions. Every PR that comes in — whether it's from a contributor or my own — needs to be reviewed.

At some point, I realized I was losing 2 hours a day just deciding what to review first. Not reviewing. Deciding.

GitHub shows PRs in whatever order they were opened. A one-line typo fix and a PR touching authentication code get exactly the same visual weight. Multiply that across 14 open PRs, and you spend more time triaging than actually reviewing.

I tried everything:

I was spending 2 hours a day triaging GitHub PRs — so I built an AI extension to fix it

I was spending 2 hours a day triaging GitHub PRs — so I built an AI extension to fix it

Related reading

I built an AI priority inbox for GitHub pull requests — and went BYOK instead…

I Built an Autonomous PR Review Agent That Runs 24/7 on My GitHub

I Built an AI Code Reviewer That Runs on 240 Repos — And a Cron System That…

What I learned building a tiny PR-review bot in 10 days

I built an AI code reviewer as a GitHub Action — here's what I learned

I Reviewed 200+ AI-Generated PRs. Here's the 4-Round Protocol I Use Now.

Related reading

I built an AI priority inbox for GitHub pull requests — and went BYOK instead…

I Built an Autonomous PR Review Agent That Runs 24/7 on My GitHub

I Built an AI Code Reviewer That Runs on 240 Repos — And a Cron System That…

What I learned building a tiny PR-review bot in 10 days

I built an AI code reviewer as a GitHub Action — here's what I learned

I Reviewed 200+ AI-Generated PRs. Here's the 4-Round Protocol I Use Now.