The State of Play

AI-assisted code review uses language models to annotate pull requests with quality, correctness, and style suggestions while keeping approval authority with human reviewers. The practice occupies a leading-edge position defined by adoption ubiquity offset by narrow value and persistent governance gaps in deployment.

June 2026 evidence reveals the core tension: suggestion-based code review works when properly configured (PanDev's 23,847-PR study: −38% review time, 2.4% defect escape in suggestion-only mode; Uber's uReview: 75% comment usefulness, 65%+ addressed), yet produces systemic failures at scale. New Relic's survey of 200 enterprise leaders documents the paradox—94% rate AI code higher quality at review time, yet 78% report increased production incidents and 82% experienced major AI-code failures in past 6 months. The central problem: code generation velocity (now 4× human review capacity per Addy Osmani's synthesis of Faros, CodeRabbit, GitClear data) has inverted the bottleneck from coding to verification. Faros's study of 22,000 developers shows AI-generated PRs wait 4.6× longer for review; 31% merge unreviewed; teams merged 98% more code with zero DORA improvement. GitHub's June 2026 move to GA pricing and SLAs for Copilot code review signals vendor confidence in leading-edge maturity, yet adoption friction remains material (Copilot's June billing change triggered user exodus; suggestion acceptance fell to 35-40% vs competitors 42-45%). The binding constraint remains not tool capability but organizational adaptation: layered review architecture (static analysis + AI + human), quality filtering infrastructure, and governance redesign required for safe deployment at velocity.

The vendor ecosystem has consolidated around platform incumbents, with specialist tools reaching hyperscale. GitHub's Copilot code review has processed 60 million reviews (10× growth since April 2025 launch), handling more than one in five reviews on the platform; June 2026 GA of Code Quality bundles code review with paid pricing ($10/active committer/month + usage consumption), signaling production-ready maturity. CodeRabbit reached 10,000+ customers with doubled revenue (Series C planned); Qodo achieved Gartner #1 ranking for codebase understanding with $120M Series B funding and 40,000+ weekly active users at named enterprise customers (Nvidia, Walmart, Red Hat, Intuit, Texas Instruments). Uber's uReview analyzes 90% of ~65,000 weekly diffs with multi-stage filtering: 75% of posted comments marked useful, 65%+ addressed. Independent testing on real AI-generated code (Inithouse, June 2026) shows Greptile leads at 82% bug detection vs CodeRabbit 44%, revealing tool differentiation by codebase-context depth. Market adoption milestone reached: 44% of development teams using AI code review (Reptile analysis, June 2026), $420M ARR category, highest penetration in enterprises (62%).

June 2026 evidence confirms persistent governance and capability gaps. New Relic's enterprise survey (200 leaders) reveals the central paradox: 94% rate AI code higher quality at review time, yet 78% report production incidents; 82% experienced major production failures tied to AI code. Faros's large-scale study (22,000 developers, 4,000 teams) quantifies the review bottleneck: AI-generated PRs wait 4.6× longer for review; 31.3% merge unreviewed; teams merged 98% more code with zero DORA improvement. Addy Osmani's synthesis across four datasets (Faros, CodeRabbit, GitClear, GitHub 60M reviews) identifies verification as the binding constraint: code output 10× faster than human review capacity; AI code produces 1.7× more issues requiring extended verification cycles. Practitioner findings document deployment friction: false-positive rates remain 5-15%, requiring mandatory human sign-off and configuration tuning (Jesse Hopkins' month-long experiment: 93% false positives week 1, improved to 3-5 per 71 valid by week 4 with retuning). Adoption friction emerged: GitHub Copilot's June billing change triggered user exodus; suggestion acceptance fell to 35-40% (competitors 42-45%), indicating pricing and quality perception barriers. Thoughtworks analysis identifies structural challenge: traditional asynchronous PR review model is 'breaking' under AI-generated code volume (500 lines in 5 seconds, but 30 minutes human review required), proposing fundamental shift to synchronous pair-based workflows. Critical architecture gaps remain: tools excel at mechanical checks (null, bounds, style) but fail on design correctness, business logic, and architectural fit. Security blind spots persist despite tool maturity: 94% OWASP Top 10 coverage for humans vs 66% for tools; human reviewers identify 41% more critical bugs.

• 2023-H2: First generation of LLM-powered PR review tools deployed in production (Beko, Ant Group research). GitHub, Amazon, and IDE vendors introduced or previewed code review features. Industry surveys showed 23% current adoption vs. 90% planned adoption, signaling high growth intent but current-stage friction. Case studies documented both capability (73.8% useful reviews, improved bug detection) and cost (increased closure time, token consumption, false positives).

• 2024-Q1: Ecosystem matured with new tooling (ThinkReview, Greptile, CodiumAI PR-Agent refinements) and GitHub Copilot Enterprise enhancements for PR context. Organic GitHub adoption visible in developer conversations. Research challenged capability claims: LLMs handle simple changes but fail on semantic complexity; reviewers anchored to AI suggestions, missing bugs elsewhere; noise-to-signal ratios remained high. Controlled experiments with developers found no time savings despite high comment acceptance rates. Critical bottleneck shifted from feasibility to signal quality and practical utility in real review workflows.

• 2024-Q2: Vendor ecosystem expanded with Amazon Q Developer GA (April), signaling major cloud platform commitment. Academic research consolidated the landscape (TOSEM roadmap on MCR's AI evolution), identifying human-AI symbiosis as the future model while acknowledging persistent capability gaps. Open-source tooling matured (PR-Agent active development, 3,729+ commits). Industry adoption surveys showed 63% of enterprises piloting or deploying by mid-2023, trending toward 75% by 2028, but analyst caution remained about actual productivity impact (coding is only 20% of development lifecycle, not the 50% vendors claim). Early-stage research continued exploring LLM-based agents for comprehensive risk prediction. The practice remained in equilibrium: rising adoption driven by vendor integration and ecosystem maturity, but value proposition contested by capability research and practitioner friction on signal quality.

• 2024-Q3: Code review adoption shifted from experimental to normalized, with >97% of enterprise developers reporting AI tool use and GitHub Copilot ranking #2 globally. Independent tooling achieved venture scale: CodeRabbit raised $16M Series A with 600+ paying organizations and Fortune 500 pilots. However, independent evaluations revealed accuracy gaps (CodeWhisperer 31.1%, Copilot 46.3%, ChatGPT 65.2% correct code generation). Duolingo case study showed 67% reduction in review time with Copilot, but enterprise surveys revealed adoption-confidence gap: 38% of US developers report active organizational encouragement despite near-universal individual adoption. Critical journalism and vendor-agnostic assessments highlighted persistent false-positive rates and signal quality concerns. The practice consolidated around normalized integration into enterprise tooling, but value proposition remained contested—velocity gains were balanced by noise, accuracy concerns, and unvalidated productivity claims at scale.

• 2024-Q4: Major cloud vendors moved from preview to GA: AWS launched Amazon Q Developer code review capability (December 2024), marking end-of-year consolidation of enterprise platform commitment. Empirical evidence from peer-reviewed ICSE 2025 study (published December 24) documented real production deployments across 238 practitioners: 73.8% comment resolution but +2.5h PR closure time, providing balanced evidence of adoption with quantified trade-offs. GitHub Copilot adoption remained strong (64.5% user retention in JetBrains survey), with Copilot and Amazon Q at 31.1% accuracy on code generation. Critical research on LLM code verification (December 2024) revealed fundamental limitations: models incorrectly validate faulty and vulnerable code, with only 25-69% improvement via guided intervention. Specialized tooling ecosystem matured (CodeAnt, CodeRabbit) with claimed large-scale deployments, but technical evaluation of Amazon Q showed strength in security detection with gaps in broad quality analysis. The practice entered end-year in normalized, mature equilibrium: ubiquitous adoption and vendor integration alongside persistent signal quality concerns and empirical evidence that velocity gains trade off PR closure time, accuracy gaps remain unresolved, and autonomous code assessment reliability is limited.

• 2025-Q1: Vendor platform expansion continued: AWS released new /review agent features in Amazon Q Developer (Feb 2025). Real-world case studies from independent organizations (Apriorit) documented 20% development cycle improvements, but critical Q1 2025 evidence mounted: industry analysis showed AI code produces 1.7x more issues with net -12% productivity impact; practitioner reports documented consistently incorrect AI suggestions and confidence-accuracy mismatches; peer-reviewed research (CHASE 2025) confirmed adoption barriers around trust and context limitations. Practice remains normalized with broad adoption but with mounting evidence that velocity gains trade off against review cycle friction and signal quality gaps.

• 2025-Q2: Deployment reached 51% of enterprise pull requests (Jellyfish analysis of 2M+ PRs, 260% YoY growth from 14% baseline). GitHub expanded platform features with custom-instructions for Copilot code review (June 2025). However, Q2 evidence revealed emerging deployment-confidence gaps: 84% of developers use AI code review but only one-third trust accuracy; 42% of developers report AI generates half or more of their code, yet one-third don't review pre-deployment (Cloudsmith report). Practitioner evidence showed velocity gains offset by verification overhead: experienced developers 19% slower with early-2025 AI tools (Metr study). Adoption surveys showed 92% face pressure to adopt AI tools with 66% concerned about job displacement. The quarter solidified market normalization but highlighted production-safety blind spots: AI-generated code volume now outpaces review capacity and human verification costs.

• 2025-Q3: Adoption plateaued while effectiveness concerns intensified. GitHub shipped copilot-instructions.md GA for organizational customization (Aug 2025); AWS released interactive Amazon Q Developer code review features (Sep 2025), signaling vendor focus on feature parity and enterprise configuration. However, deployment data reversed earlier headlines: Jellyfish analysis of 400 companies showed agents on only 22% of reviews with 18% resulting in code changes. Large-scale empirical study of 16 AI code review tools found 0.9-19.2% effectiveness vs. 60% for humans. Google DORA survey revealed adoption-trust paradox: 90% use AI but only 24% trust it "a lot" (Sep 2025). Bain report documented only 10-15% productivity gains with METR evidence showing developers 5-19% slower due to verification overhead. The quarter marked consolidation around platform ubiquity without commensurate effectiveness gains. Code review effectiveness, not capacity, emerged as the binding constraint.

• 2025-Q4: Adoption surge met deepening trust crisis. Code review agent adoption climbed to 51.4% in engineering teams (Oct 2025, from 14.8% at year start), with 90% of teams using AI assistance and 41% of code output AI-generated/assisted. Vendor consolidation accelerated: AWS deprecated CodeGuru Reviewer and consolidated code review into Amazon Q Developer GA (Nov 2025). Yet sentiment data painted a concerning picture: Stack Overflow's 49,000-developer survey (Dec 2025) revealed 80% adoption but trust fell to 29%, with 45% frustrated by "almost right" AI code requiring rework. Practitioner evidence documented unintended consequences: GitClear analysis found 8x code duplication and 37.6% vulnerability increase when same AI model reviewed its own output (Qodo, Dec 2025); team case study showed initial metric gains evaporated as AI review eroded mentorship and code homogeneity (Dec 2025). The quarter crystallized the effectiveness paradox: infrastructure and tooling achieved ubiquity, but signal quality, trust, and verification overhead remained unresolved. The binding constraint shifted from availability to deployment maturity.

• 2026-Jan: Bottleneck revealed in first-month research cascade. Independent empirical studies quantified the scalability crisis: MSR 2026 analysis of 33,707 AI-authored PRs found 28.3% instant-merge rate but sustained high review effort in iterative cases, with top 20% of highest-effort PRs consuming 69% of total labor (mining-challenge.2026). MSR 2026 peer-reviewed study showed AI PRs generate positive reviewer sentiment but carry higher redundancy and lower code reuse, masking technical debt (arxiv.2601.21276). Sonar developer survey (1,100+, Jan 2026) documented verification paralysis: 72% daily AI tool use, but 96% doubt correctness and only 48% verify before commit; 38% report AI review verification harder than human review. Baytech synthesis (Jan 2026) quantified productivity paradox: METR 2025 RCT shows experienced developers 19% slower due to verification overhead despite psychological belief in 20% gains. Market analysis (Zylos, Jan 2026) confirmed mainstream penetration: 84% developer adoption, 20% of enterprises using AI to review 10-20% of PRs, but leading tools detect only 42-48% of runtime bugs with 5-15% false-positive rates. Practitioner frameworks emerged (Sancho, Jan 2026) proposing hybrid three-confidence-dimension model to address review overload (AI PRs regularly exceed 2,000 LOC, far above human cognitive limits of 200-400 LOC/hour). Month consolidated the mature-stage diagnosis: infrastructure ubiquity achieved, but signal quality, review capacity scaling, and workflow adaptation remain unresolved. Binding constraint identified as hybrid-model organizational design, not tool capability.

• 2026-Feb: Systematic reliability research published in arXiv preprint (Feb 28) reveals fundamental failure modes: LLMs frequently misclassify correct code as non-compliant, with higher misjudgment rates under detailed prompts requiring explanations. Real-world deployment data continues to show paradoxical outcomes: AWS product page reports BT Group at 37% and NAB at 50% suggestion acceptance in production (escalating to 60% with codebase customization), yet industry aggregation (10x.pub synthesis, Feb 11) quantifies the "40% code review quality deficit" with 1.7x higher issue density in AI-reviewed code, PR sizes 18% larger, and incidents 24% higher. Senior engineers report 3.5x longer verification cycles when reviewing AI suggestions. Code review time increased ~91% despite AI adoption (Faros AI, Feb 2026 analysis), contradicting DORA improvement claims. Comparative tool testing (Manus, Feb 13) across 9 platforms found significant variance in detection quality on security-critical logic (RBAC, auth, middleware). Month crystallized the maturity plateau: tooling ubiquity (AWS, GitHub, CodeRabbit all scaling) coexists with unresolved signal-quality gaps and emerging organizational concern about unintended consequences—mentorship erosion, junior pipeline collapse (60% drop in entry-level hiring since 2022), and senior engineer burnout from extended verification cycles. The core tension remains unresolved: code generation velocity now outpaces both review capacity and organizational ability to maintain code quality standards and engineering culture.

• 2026-Mar: Market maturation and organizational response converge. GitHub reported 60 million Copilot code reviews since April 2025 launch (10x growth), handling >20% of all reviews on platform with agentic memory and repository context, while CodeRabbit announced 10,000+ customers with doubled revenue and $86M total funding (Series C planned). Large-scale empirical research definitively quantified the bottleneck: LinearB analysis of 8.1M PRs from 4,800 teams showed AI code waits 4.6x longer for review start but reviews 2x faster once started (net slowdown); acceptance gap of 51.7 percentage points (32.7% AI vs 84.4% human) directly mirrors trust gap (96% distrust, 48% verify). Independent tool comparison (Cotera) found Copilot achieves 64% actionable suggestion rate, CodeRabbit 58%, with critical limitation: lack of codebase context awareness. HubSpot case study documented organizational adaptation: internal Sidekick agent evolved from infrastructure-heavy Kubernetes approach to focused "Judge Agent" filtering low-value feedback before publication, reducing latency 90% and establishing feedback quality (not volume) as constraint. Amazon formalized verification response: mandatory senior engineer sign-off on all AI-assisted code following March 5 outage, reflecting 96% correctness distrust and 48% verification gap. Production incident case study documented 12 subtle vulnerabilities missed by traditional review, requiring AI-specific security checklist to achieve 94% detection at 47% review time cost. Atlassian peer-reviewed study of 1,900+ repos found AI tools resolve only 38.70% of security issues vs 44.45% human, with critical blind spots in business logic and architecture-level risks. Quality-speed tradeoff crystallized: cycle time dropped 24% but defect density increased 1.7x. Month confirmed leading-edge diagnosis: tooling ubiquity and vendor consolidation achieved, but review capacity saturation, quality-speed tradeoffs unresolved, and organizational adaptation (workflow redesign, verification infrastructure, governance) critical differentiator between successful and failing deployments. The binding constraint shifted from tool availability to organizational design capacity.

• 2026-Apr: Tool capability evaluation reaches maturity with convergent benchmarking and incident evidence. Independent benchmarks quantified effectiveness limits: Martian's 200,000+ PR analysis across 17 tools shows 50-60% F1 scores with CodeRabbit leading at 51.2%; Entelligence's evaluation on 67 real production bugs finds even best tools (Entelligence 47.2%, CodeRabbit 33%, Copilot 22.6%) miss >50% of real bugs—establishing that current tools cannot be relied upon for comprehensive review. Formal verification research (Z3 SMT solver on 3,500 artifacts) reveals critical generation-review asymmetry: models catch their own vulnerabilities 78.7% of the time in review mode despite generating them 55.8% by default, validating AI code review value but also confirming organizational need for multi-layer verification. Real-world deployment metrics widen the concern: Fortune 500 financial services (40+ engineers with Claude Code and Copilot) reported 52% code review time increase despite 30% PR volume increase, with senior engineers spending 6-8 hours/week on AI-generated reviews (up from 4-5 hours), forcing fundamental workflow redesign. GitHub shipped new API metrics (total_merged_reviewed_by_copilot, median_minutes_to_merge) signaling production maturity and enabling independent ROI measurement. Trust erosion incidents mounted: Copilot injected promotional text into 1.5M+ PR descriptions without developer control, documenting integrity risks in code review surfaces; Branch8's managed engineering firm (200+ teams) published post-incident governance requiring 3% engineering capacity overhead to safely operate AI-assisted review. CodeRabbit analysis of 470 GitHub PRs confirmed quality paradox: AI code produces 1.7x more issues (10.83 vs 6.45 per PR), 2.74x higher security vulnerabilities, 3x worse readability, with 75% manual review adoption yet incidents still surging 23.5%. Late-month evidence (April 15-28) reinforces constraints: JetBrains empirical research (800-dev longitudinal study presented at ICSE 2026) confirms workflow shifts reveal adoption-value gaps; Google deployment case study documents 75% of new code AI-generated with engineers spending 11 minutes reviewing each changelist focused on security and architecture; Cloudflare case study shows multi-agent orchestration (7 specialized reviewers) deployed across tens of thousands of PRs; Black Duck's OSSRA report identifies critical governance failure (only 24% comprehensive review rate correlating with 107% vulnerability surge); practitioner analysis confirms effectiveness ceiling at 50-60% with material post-merge defect rates. GitHub's expanded metrics API (active/passive user tracking) signals feature maturity and enterprise adoption readiness. Month consolidated April evidence into clear picture: tooling capability hitting hard limits (50-60% effectiveness ceiling), organizational costs mounting (52% review time increase), governance gaps widening (24% review rate), and structural gaps (generation-review asymmetry, business-logic blind spots) requiring governance and workflow redesign rather than tool improvement. The practice approaches plateau: ubiquitous adoption without commensurate value delivery remains the defining constraint.

• 2026-May: Evidence cascade reveals both positive deployment outcomes and critical safety/capability gaps. PanDev Metrics' comprehensive empirical study of 100 B2B teams (23,847 PRs over 12 months) documented that suggestion-only code review configuration achieved −38% review time with 2.4% defect escape—properly configured suggestion-based review delivers value when signal quality is prioritized. Hyperscale confirmation: Uber's uReview processes 90% of ~65,000 weekly diffs with 75% comment usefulness; CodeRabbit reached 8,000+ paying customers, 2M+ repositories, and ~$40M ARR (#1 GitHub Marketplace app) with documented customer outcomes (Groupon 86h→39m review time). Qodo 2.0 processes 20,000+ PRs daily with Gartner #1 ranking for codebase understanding and named enterprise customers (Nvidia, Walmart, monday.com). Independent benchmark (Claude Code vs. 47 known bugs) found Claude Code detected 55% vs 31% senior human baseline, though critical limitation remains: cannot verify business alignment. GitHub's metrics API expansion (May 2026) added suggestion type breakdowns per category. Critical safety disclosure: prompt-injection vulnerability (CVSS 9.4) affecting Claude Code, Copilot, and Gemini code review agents enables credentials harvest via crafted PR titles/comments with zero infrastructure requirements. Negative signal reinforced: independent benchmark across 47 production repos showed human reviewers identify 41% more critical bugs than AI toolchain, achieve 0% false positives on critical issues vs 12% AI, and cover 94% OWASP Top 10 vs 66% AI. Code churn worsened: up to 9× higher with AI tools (GitClear); 66% of developers report AI output "almost correct but still flawed." Month confirmed: suggestion-based review can work at hyperscale with rigorous filtering, but baseline effectiveness remains below human reviewers and the code review agent attack surface is now an active security threat.

• 2026-Jun: Evidence cascade crystallizes governance as the binding constraint. Microsoft shipped GitHub Copilot code review in limited public preview for Azure Repos (June 2); GitHub released Copilot code review GA (July 20 announcement June 16) bundled with Code Quality product tier at $10/active committer/month + usage consumption, signaling vendor confidence in production-scale maturity. GitHub's June releases included Agent Skills and MCP server integration (enabling issue-tracking context injection into reviews) and Medium analysis tier (routing complex PRs to higher-reasoning models). Market adoption milestone: 44% of teams using AI code review (Reptile, $420M ARR category). New Relic's survey of 200 enterprise leaders reveals central paradox: 94% rate AI code higher quality at review; 78% report production incidents; 82% experienced major AI failures. Faros study (22,000 developers, 4,000 teams) quantifies bottleneck: AI PRs wait 4.6× longer for review; 31.3% merge unreviewed; 98% more code merged with zero DORA improvement. Addy Osmani (O'Reilly) synthesizes four datasets documenting that code generation 10× faster than review capacity; AI output 1.7× more issues. Independent testing reveals tool differentiation by context depth: Greptile 82% vs CodeRabbit 44% bug detection on AI-generated code (Inithouse, 10-tool comparison). Copilot adoption friction emerged: June 1 usage-based billing triggered exodus; suggestion acceptance fell to 35-40% vs competitors 42-45%. Thoughtworks analysis identifies structural challenge: asynchronous PR model 'breaking' under AI velocity; proposes synchronous pair-based redesign with AI as co-reviewer. Practitioner evidence documents deployment friction: configuration tuning essential (Hopkins: 93% false positives week 1 → 3-5 per 71 by week 4); false-positive rates 5-15% remain barrier despite tool availability. Alibaba's Open Code Review (2M+ developers) documented hybrid architecture (deterministic preprocessing + LLM) outperforming single-model tools with 1/5th token cost. June diagnosis: tooling and vendor ecosystem mature; architectural features (MCP, tiered analysis) address context gaps; fundamental constraint is organizational adaptation—layered review architecture (static + AI + human), quality filtering, and verification governance required for safe velocity. Single-model code review has inherent blind-spot problem solved by parallel cross-provider approaches; repository-scale cross-file reasoning identified as real bottleneck. The binding constraint is no longer tool availability but organizational design maturity.

• 2026-Jul: Review capacity crisis confirmed across converging large-scale datasets. Faros (22k developers, 4k teams) and Addy Osmani's O'Reilly synthesis across four datasets (Faros, CodeRabbit, GitClear, GitHub 60M reviews) both establish the same bottleneck: PR velocity 10× faster than review capacity; 31.3% of AI PRs merge unreviewed; AI output carries 1.7× more issues requiring extended verification. New Relic enterprise survey (200 leaders) captures the resulting paradox: 94% rate AI code higher quality at review time, yet 78% report production incidents and 82% experienced major AI-code failures—confirming that review-time assessment is structurally disconnected from production outcomes. GitHub Code Quality GA (scheduled July 20) and the Thoughtworks proposal to abandon async PR review in favour of synchronous pair-based workflows signal that the industry is treating the review architecture itself, not tool capability, as the fixable variable. Additional late-July evidence sharpened the diagnosis: Augment's synthesis (42% of code now AI-generated, 96% reviewer distrust, review time up 91%) proposed a six-layer verification stack as the missing infrastructure layer, while Zocdoc demonstrated governance-first deployment working in production—hybrid AI-plus-mandatory-human-approval review lifted PRs merged per engineer 80% and cut change failure rate 75% in a regulated healthcare environment. Wiz security research disclosed GhostApproval, a symlink-based spoofing flaw letting attackers substitute the file shown in six AI tools' approval dialogs to gain SSH access, exposing a structural maturity gap in agentic review safety. A longitudinal study of 802 developers and 196K PRs confirmed reviewer load doubled and merge cycles lengthened under AI-assisted coding, and a stratified analysis of 3,100 practitioner opinions built a causal theory naming review quality as the single control point determining whether AI helps or harms software outcomes. Career Design Center's "type" team offered a counter-example of successful governance: YAML-configured CodeRabbit checks let a 15-year legacy modernization move from mandatory 2-person to 1-person review.

• 2026-Aug: GitHub shipped GA of Agent Skills and MCP integration in Copilot code review across all paid tiers, while SonarSource launched Gitar, an agentic review tool with CI-validated fixes, signaling vendor consolidation toward automated-fix capabilities. Independent benchmarks reinforced the quality gap—CodeRabbit's 470-PR analysis found AI code carries 1.7x more issues (security 2.74x higher), a 480-PR three-tool comparison ranked Copilot ahead of Claude Code and CodeRabbit on genuine bug capture, and LinearB's 8.1M-PR study confirmed AI PRs wait 4.6x longer for review with a 51.7-point acceptance gap versus human-authored code.