Get a fast, useful first review on every pull request. Code Reviewer is generally available with paid Jira and Teamwork Collection licenses.

As teams adopt AI coding agents, they’re writing code faster and in greater volume. That puts pressure on the rest of the software lifecycle, and code review especially has become one of the biggest constraints on getting software into production.

Developers now face more code to review and bigger changes. According to our Q3 State of AI Impact in Engineering Report, teams that rely heavily on AI to write code now wait more than twice as long for a human review on a pull request (71 minutes, up from 32). And median pull request size has more than doubled in the past year from 46 to 102 lines of code. Human review alone is struggling to keep up, and that’s the problem Code Reviewer is built to solve.

Code Reviewer is available now as part of your paid Jira or Teamwork Collection subscription

Code Reviewer is an AI agent that reviews pull requests in Bitbucket Cloud and GitHub (with GitLab coming soon). Because it’s deeply connected to Jira and the Teamwork Graph, each review is grounded in your context. That means every change gets a fast and useful first review, and your teammates can focus on the feedback that needs human judgment.

Code Reviewer leaves inline comments to flag issues and suggest fixes authors can apply right in the pull request. It catches bugs, logic errors, security risks, and maintainability issues. It checks pull requests against acceptance criteria in linked Jira work items. And for large changes, it also adds a summary to help reviewers get oriented.

Every comment should be worth a reviewer’s time. That’s why a built-in quality filter removes low-value comments, so the feedback that reaches your team is signal, not noise.

We’ve seen the results on our own code. Since rolling out Code Reviewer internally, median pull request cycle time has dropped by 31%. And 39% of Code Reviewer’s comments led directly to a code change in the next commit.

Bring your coding standards into every review (beta)

With Standards, a new feature available in beta, you can document your organization’s coding standards and assign them to specific repositories. Code Reviewer then checks each pull request against that repository’s standards, so your requirements are applied consistently, no matter who’s reviewing. Sign up for the beta here.

Your code stays yours, and you stay in control

Trust and safety are built into how Code Reviewer works. Each review runs in a temporary, isolated environment that’s deleted as soon as the review finishes. Your code isn’t stored afterward, and it’s never used to train models.

Admins decide where automatic reviews run (which workspaces and which repositories) and can switch any of them back to manual or turn Code Reviewer off entirely.

Get a review on every pull request, automatically

Code Reviewer is on by default for eligible sites, in manual mode. It only reviews a pull request when the author asks. To get the most out of Code Reviewer, turn on automatic review, so every new pull request gets an AI first pass as soon as it opens, without anyone having to ask. Watch the demo or read our instructions below for how to set it up.

How to turn on automatic review

Before you start: connect your code to Jira.

  • GitHub: install the GitHub for Atlassian app from the Atlassian Marketplace.
  • Bitbucket Cloud: connect your Bitbucket workspace to your Jira site.

Bitbucket Cloud

To set up automatic review, you’ll need to be a workspace admin to change workspace settings. Repository admins can change repository settings.

  1. Open the settings. In Bitbucket, go to Workspace settings > AI, then select Code Reviewer.
  2. Choose when it runs. Change the trigger from Manual triggers only to Every new pull request. For full coverage, choose Every commit instead, so each new commit to a pull request is reviewed again.
  3. Make it the default. Select Set as default to apply this setting to every repository in the workspace.
  4. Adjust a single repository (optional). Go to Repository settings > Features > Code review.

GitHub

GitHub repositories are managed from Jira. You’ll need to be a Jira site admin to set up automatic review.

  1. Open the settings.
    • Jira site admins: go to Jira site settings > Developer AI > Reviewer settings, then select GitHub.
  2. Choose your organization. Select your GitHub organization, then select Manage settings for all repositories.
  3. Turn on automatic review. Set the trigger to When PR is created, then select Apply to all repositories in this organization.
  4. Adjust a single repository (optional). Select any repository in the list to change its settings and see more options.

Get great results from day one

Code Reviewer is only as good as the context it can see. Two habits make the biggest difference:

  • Link pull requests to Jira work items. Include the work item key (for example, PROJ-123) in the branch name or pull request title so Code Reviewer can check if changes are aligned with your Jira work item.
  • Write specific acceptance criteria. “Show an error message when the upload exceeds 10 MB” gives Code Reviewer far more to check than “Handle errors.”

AI is changing how fast teams can write code. Code Reviewer helps make sure review keeps up. Turn on automatic review, and give every pull request a fast, grounded first pass.

Code Reviewer is generally available as part of your paid Jira or Teamwork Collection subscription. Code Reviewer uses Rovo credits, which are charged under our usage-based pricing policy.

Questions? Visit the Code Reviewer documentation. Feedback? Share your thoughts through our in-product feedback collector.