From better static analysis to smarter test generation: here’s everything we shipped in the last 90 days.
CodeRabbit just hit 12 million PRs, 70,000 installs, and climbed to the first page on the GitHub Marketplace.
Huge thanks to every developer for making us a part of their workflow.
But behind the scenes, we’ve also shipped some of our most impactful features, covering languages like Python, PHP, Lua, Rust, Ruby, and tooling from VS Code to Cursor. This post covers all changelog updates from May through early July.
July 2025
Jupyter Notebook Support via nbqa
(July 10)
CodeRabbit now supports Python static analysis inside Jupyter Notebooks using nbqa
. This brings notebook linting support to tools like Ruff, Flake8, and Pylint.
- Works directly on
.ipynb
files - Enforces style and quality across notebooks and scripts
- No extra configuration needed
Useful for teams working in data science, research, and hybrid Python codebases.
Flake8 Integration (July 3)
We’ve added support for Flake8, a Python linting tool that combines:
-
PyFlakes
for logic errors -
pycodestyle
for formatting violations -
McCabe
for complexity checks
You can now enable Flake8 directly in your CodeRabbit static analysis configuration.
Expanded Code Guidelines Detection (July 1)
CodeRabbit now automatically detects and applies your team's coding standards by scanning for additional configuration files across your codebase:
**/.cursorrules
.github/copilot-instructions.md
**/.cursor/rules/*
**/.clinerules/*
**/.rules/*
**/.windsurfrules
**/CLAUDE.md
These patterns are used to fine-tune reviews based on your preferred rules. You can manage them in the Knowledge Base section of your project settings.
June 2025
PHPMD and PHPCS for PHP (June 27)
Static analysis support for PHP has been significantly expanded:
- PHPMD (Mess Detector) identifies dead code, complexity issues, and common bugs
- PHPCS (CodeSniffer) enforces PSR-1, PSR-2, PSR-12, and custom coding standards
Both tools are configurable through their standard settings files or within CodeRabbit.
HTMLHint and Checkmake Support (June 11)
Two new lint tools are now available:
- HTMLHint helps enforce HTML best practices and accessibility
- Checkmake provides linting for Makefiles, improving consistency in build scripts
These additions are useful for frontend engineers and teams working with CI-heavy repositories.
Unit Test Generation (Early Access, June 10)
Unit test generation is now available in early access. CodeRabbit can generate test cases directly from your code changes:
- Understands your project’s testing style and structure
- Covers edge cases, error paths, and core logic
-
Works via comment trigger:
@coderabbitai auto-generate unit tests
Also available via a checkbox in walkthrough comments
You can edit, extend, or disable generated tests as needed.
Dotenv Linter and Pylint Support (June 5)
Two new static analysis tools added:
-
Dotenv Linter checks
.env
files for invalid syntax, duplicated keys, and misconfigurations - Pylint, a Python linter that enforces style, detects code smells, and improves maintainability
These tools integrate seamlessly with your existing workflows.
May 2025
Brakeman and Clippy Integration (May 25)
We’ve added static analysis support for both Ruby and Rust:
-
Brakeman scans Ruby on Rails apps for security vulnerabilities across
.rb
and.erb
files - Clippy is the Rust linter that helps enforce idiomatic Rust and catch common pitfalls
You can customize their behavior via configuration files or CodeRabbit’s tool settings.
Lua Static Analysis with Luacheck (May 19)
Support for Luacheck, the standard linter for Lua, is now live.
It detects unused variables, incorrect scope usage, and enforces style across Lua projects.
Editor Integrations: VS Code, Cursor, Windsurf (May 14)
CodeRabbit reviews are now available inside VS Code and its forks, including Cursor and Windsurf.
- Inline, real-time code reviews
- One-click “Fix with AI” for complex suggestions
- Zero setup required, install the extension
- Supports multi-language projects (JavaScript, Python, PHP, Go, Ruby, and more)
This makes it easier to review, fix, and commit without needing to switch between the editor and GitHub.
What’s Next
Over the next quarter, we’ll continue expanding support across tools, editors, and programming languages. Our goal remains the same: to help developers ship faster, safer, and smarter code, with less friction.
To stay updated, join the CodeRabbit Discord or follow @coderabbitai on X.
Top comments (0)