What your review queue's ranker can and cannot see
A team with more open pull requests than review hours does not need another reviewer first. It needs something that decides which pull request to lo…
Open Source
⚑ Сообщить о проблемеПоследние новости Open Source от Tech News
Все темы
AI
agents
ai
api
architecture
automation
backend
beginners
career
database
devchallenge
devops
discuss
javascript
linux
llm
machinelearning
mcp
opensource
performance
productivity
programming
python
react
security
showdev
testing
tutorial
typescript
webdev
Which of your rule files the reviewer actually reads
Every AI review tool claims it reads your AGENTS.md or CLAUDE.md. What decides whether your standards actually land is which rule wins when two appl…
The artifact worth reviewing when agents write the code
GitHub's Security Lab reported 24 Android vulnerabilities found by an AI security agent, and the part worth copying is what ended up version-control…
Where AI review saves time: the write-back, not the analysis
A tool that "supports Azure DevOps" may only be able to read your pull request. What cuts review time is the write-back: posting an inline comment w…
Your pull request review time is mostly waiting and rework
Time to merge is the number teams quote when they say AI review sped things up. It bundles at least three separate costs, and reading the diff is on…
Verus proves Rust correct for all inputs. Code review still can't define "correct."
Amazon shipped a blog post on Verus, their Rust verifier used in Firecracker and AWS Lambda. Verus doesn't review your code. It proves it: annotated…
When review time plateaued, reviewers had stopped reading
Salesforce posted the number that most teams report, then said the part most teams leave out. In "Scaling Code Reviews: Adapting to a Surge in AI-Ge…
Cycle time and review time are not the same metric
"Reduce PR review time with AI" claims quote at least two different clocks, and the gap decides whether a number tells you anything. Atlassian repor…
Counting bugs is the hard part of comparing AI review tools
Model benchmarks for code review usually report the same two numbers: how many bugs the tool found, and how many of its comments were actually right…
Reduce PR review time with AI: what the 45% claim leaves out
When a team asks how to cut pull request review time with AI, the answer they get is usually a vendor number. Atlassian says Rovo cut PR cycle time…
Where AI review pays: the codebase matters more than volume
Field note. Claims checked as of 2026-09-12. Primary source: Michels et al., "Vibe Coding: Practice, Performance, Productivity, and Risk - A State-o…
Review time is up 441% under vibe coding. That is the real problem.
A state-of-the-art review of the first body of evidence on AI-assisted development was posted to arXiv on 20 Aug 2026. It is a preprint, not itself…
Microsoft's PRAssistant number is real, and it's a floor, not a promise
Microsoft published the rare thing in this space: a first-party, attributed throughput number for AI code review. PRAssistant ran across 5,000 inter…
The GNU strip backdoor is the case AI code review can't see
This paper (arxiv 2607.24888) is worth a stop if you evaluate AI code review. It shows Ken Thompson's trusting-trust attack is not compiler-specific…
How I actually eval AI code review tools (no vendor numbers)
Every AI code review tool ships a blog post full of precision numbers. "98% precision, 87% recall, 40% fewer bugs shipped." I stopped trusting those…
One "Fix This Code" Prompt Away from a Production Incident
This article was originally published on LucidShark Blog . A developer opened their AI coding tool, pasted in a critical authentication module, and…
Greptile Review 2026: 82% Bug Catch Rate, the $1/Review Trap, and Who Should Pay $30/Month
This article was originally published on aicoderscope.com Every other AI code reviewer looks at your diff. Greptile indexes your entire codebase fir…