# How Clerk uses CodeRabbit

**40%**: “Thanks to CodeRabbit, the Clerk team was able to merge their PRs 40% faster.”

As published on [coderabbit.ai](https://www.coderabbit.ai/case-studies/inside-clerks-40-percent-faster-merge-workflow-with-coderabbit). Captured by usedby on 2026-10-06.

- Company: [Clerk](https://www.usedby.ai/companies/clerk.md)
- Tool: [CodeRabbit](https://www.usedby.ai/tools/coderabbit.md)
- Industry: [DevTools & Infrastructure](https://www.usedby.ai/companies/industry/devtools-infrastructure.md)

## What the story says

Clerk's engineers use CodeRabbit as an always-on first reviewer for pull requests, including in IDEs and CLIs. It flags security weaknesses, OAuth spec violations and edge-case bugs before human reviewers look at the code, so people can focus on design and architecture.

Summary written by usedby from the source page, in English. The figures are those of CodeRabbit and Clerk, not ours.

> Thanks to CodeRabbit, the Clerk team was able to merge their PRs 40% faster. Brandon credits CodeRabbit for catching bugs early, before they trigger rejection cycles..

- **70%**: “Clerk’s 70% acceptance rate of all potential bugs CodeRabbit flags shows the tool has earned trust.”

> Since adopting CodeRabbit, our confidence is up and our bugs are down; it catches the edge cases humans skim past and helps us merge faster with more confidence.
>
> Brandon Romano, Senior Staff Software Engineer

## What usedby checked

We compared the story with its live page on 2026-10-06.

- Checked: the figure 40% is printed word for word on the page, near the name of Clerk.
- Checked: the passage quoted above is copied word for word from the page, near the name of Clerk.
- Checked: Clerk uses CodeRabbit. Confirmed line. Latest check across sources: 2026-10-06.
- Not checked: the result itself. We quote it; we did not measure it.

---
Source: https://www.usedby.ai/case-studies/clerk-coderabbit · How we check: https://www.usedby.ai/methodology