惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

V
Visual Studio Blog
U
Unit 42
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
The GitHub Blog
The GitHub Blog
Microsoft Azure Blog
Microsoft Azure Blog
有赞技术团队
有赞技术团队
Stack Overflow Blog
Stack Overflow Blog
爱范儿
爱范儿
博客园 - 司徒正美
Vercel News
Vercel News
I
InfoQ
GbyAI
GbyAI
C
Check Point Blog
B
Blog RSS Feed
Martin Fowler
Martin Fowler
B
Blog
MyScale Blog
MyScale Blog
腾讯CDC
博客园 - Franky
Blog — PlanetScale
Blog — PlanetScale
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Hugging Face - Blog
Hugging Face - Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
博客园 - 三生石上(FineUI控件)

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
I built an AI priority inbox for GitHub pull requests — a...
Projekta2 · 2026-06-20 · via DEV Community

Projekta2

The problem

GitHub shows your pull requests in whatever order they happened to be opened — not in the order they actually need your attention. A one-line typo fix and a PR touching authentication code get exactly the same visual weight in your inbox. Multiply that across a dozen open PRs and you spend more time deciding what to look at than actually reviewing.

What I built

PR Focus is a Chrome extension (Manifest V3) that sits on top of GitHub's PR pages. It combines three signals into a single priority queue:

  • CI status — failing checks bubble up
  • PR age — stale PRs don't get forgotten
  • AI risk score (0–100) — weighted toward changes touching auth, database, or infra code

Each PR also gets a plain-English summary generated from the actual diff (not the title someone wrote at 11pm), and you can generate an approve / request-changes draft review in one click, edit it, and send — without leaving the extension.

Why BYOK instead of my own AI backend

This was the decision I spent the most time on. Running my own AI backend would have meant:

  • A server in the data path of every PR diff users review — a much bigger trust ask, especially for private repos.
  • Either eating the AI cost myself (unsustainable as a solo dev) or marking it up into a subscription.

Going BYOK (bring your own key — OpenAI, Groq, Mistral, or a local Ollama instance) flips both of those:

  • Your GitHub token and AI key live in chrome.storage.local. There's no server of mine in the path — PR diffs only ever go to the AI provider you explicitly configure.
  • Groq's free tier is generous enough to run the AI features for free for most individual workflows. You're paying provider cost directly, with zero markup, if you pay anything at all.

How it's built

  • Manifest V3 — required rethinking persistence patterns that worked under MV2's persistent background page; service worker lifecycle and content script injection needed more careful handling.
  • GitHub REST + GraphQL APIs rather than DOM scraping — more upfront work, but it doesn't break every time GitHub ships a frontend redesign.
  • IndexedDB for local data persistence (capture history, stats).
  • Gumroad for license validation instead of a subscription backend — much less infrastructure to maintain solo.

Pricing model

Free tier: multi-account GitHub switching, PR sorting/export, stale-PR notifications.
PRO ($9.50 one-time, currently 50% off the $19 regular price): AI summaries, risk scoring, one-click draft reviews, full stats history, AI-based priority sorting. No subscription — pay once, own it.

What's next

Currently solo-maintained, iterating on feedback from the first wave of GitHub stars and a community-contributed PR that got merged — which, honestly, felt like a bigger validation moment than any launch metric so far. Performance-regression detection and broader language support (Python, Go) are next on the roadmap.

Try it: https://chromewebstore.google.com/detail/pr-focus-ai-pro/ememaiabefeojkccjclglcmbjmdpnaoe
Landing + demo: https://projekta2.github.io/pr-focus-landing/

Feedback welcome — especially from anyone who's built browser extensions against the GitHub API, or who has opinions on BYOK UX.