Topic · 12 stories
12 stories tagged code-review on AI Tamer, newest first.
Thomas Dohmke's Entire launches a Git-compatible forge with Trails, review agents, merge Gates, GitHub mirroring and two MIT-licensed memory CLI plugins.
Anthropic's 15 October article makes Code Review generally available for Team and Enterprise. Eligible Enterprise orgs can claim credits by 15 January 2027.
Committer Peter Eisentraut says 8 to 10 significant features were reverted from PostgreSQL 19 in beta. He points to LLM-assisted review finding defects faster and security work cutting review time.
NVIDIA's open-source Boro is a Rust CLI for AI-assisted Linux kernel review, backports and build-boot-test runs before a series goes public. Its LPC 2026 talk asks what could fold into Sashiko.
SpaceXAI joined the Omacom Foundation as a Founding Corporate Patron with $1.5 million in Grok tokens. Omarchy says Grok 4.7 and later will help power Omabot, its pull request review agent.
Roman Gushchin's Linux Plumbers 2026 slides say Sashiko, an agent that reviews kernel patches, has finished 191,000 reviews. The same deck cites 1,277 upstream commits and 463 CVEs whose fixes name the tool.
GitHub's 5 October 2026 post introduces ReviewBench: 219 public pull requests shaped against 103.9 million GitHub PRs, with multi-source labels and a leaderboard that includes Copilot code review.
Dependabot grouping rules decide which security fixes arrive together. Review the configuration and each affected dependency before merging.
GitHub's 2 October 2026 changelog says Copilot code review is requestable from REST and GraphQL, with an effort level on each call. Balanced, which took effect on 28 September, is the default.
A reviewer finds mistakes faster when a diff holds one change, shows moved code as moved, and comes with a clear description. Here is what Google's review guide and the git manual say about it.
A practical review order for AI-generated code: check the diff, test the behavior, verify APIs and errors, then inspect security-sensitive paths.
A nearly full disk on a machine running AI review sessions: what was using the space, the explanation I checked first, and the rule that would have prevented it.
