CodeRabbit logoCodeRabbit logo
AgentEnterpriseCustomersPricingBlog
  • Docs
  • Trust Center
  • Contact Us
  • FAQ
  • Reports & Guides
Log InGet a free trial

Products

AgentDiscordPull Request ReviewsIDE ReviewsCLI ReviewsPlanOSS

Navigation

About UsFeaturesFAQSystem StatusCareersDPAStartup ProgramVulnerability Disclosure

Resources

BlogDocsChangelogCase StudiesTrust CenterBrand GuidelinesReports & Guides

Contact

SupportSalesPricingPartnerships

By signing up you agree to our Terms of Use and authorize CodeRabbit to provide occasional updates about products and solutions. You understand that you can opt out at any time and that your data will be handled in accordance with CodeRabbit Privacy Policy

footer-logo shape
Terms of Service Privacy Policy

CodeRabbit, Inc. © 2026

Code guidelines: bring your coding rules to CodeRabbit

by
Edgar Cerecerez

Edgar Cerecerez

July 02, 2025

2 min read

July 02, 2025

2 min read

  • Using Code Guidelines
  • Why it matters
  • What's next?
Back to blog
Cover image

Share

Share on RedditShare on XShare on LinkedIn

Cut code review time & bugs by 50%

Most installed AI app on GitHub and GitLab

Free 14-day trial

Get Started

Catch the latest, right in your inbox.

Add us to your feed.RSS feed icon
newsletter decoration

Catch the latest, right in your inbox.

Add us to your feed.RSS feed icon

Keep reading

Close the loop after every merge: the agent that reviewed your PR can now follow through

Close the loop after every merge: the agent that reviewed your PR can now follow through

Post-Merge Actions use pull request context to handle changelogs, documentation, tickets, and other work that should happen after merge.

GPT-5.6 Sol and Terra: Where they fit for coding agents and code review

GPT-5.6 Sol and Terra: Where they fit for coding agents and code review

OpenAI’s GPT-5.6 family includes capability tiers: Sol as the flagship model, Terra as the lower-cost option, and Luna as the fastest, lowest-cost tier.

The case for monorepos, and what they cost you

The case for monorepos, and what they cost you

Monorepos keep shared code in sync but make every bad PR everyone's problem. Here's when to commit to one, when polyrepo wins, and how to review at scale.

Get
Started in
2 clicks.

No credit card needed

Your browser does not support the video.
Install in VS Code
Your browser does not support the video.

If you're using or have tried out Cursor or another AI coding tool (who hasn't?), chances are you've also seen the downsides of it. Maybe you’re having to repeat how to structure the project when creating new files. Or maybe you're using shadcn/ui for UI components. Or maybe when you want to run a build that requires another command to build a backend dependency first.

Cursor, Windsurf, Copilot, and other AI coding agents addressed this problem by adding support for reusable, scoped instructions that can be read on every ask – or when requested. Smart move!

Using Code Guidelines

CodeRabbit will automatically detect your coding rules for:

  • Cursor .cursorrules

  • GitHub Copilot .github/copilot-instructions.md

  • Cline /.clinerules/*

  • Windsurf /.windsurfrules

  • Claude /CLAUDE.md

  • And more

With Code Guidelines, these rules are used as context on every PR review.

We also support adding your own rules by specifying a custom file pattern. Got your guidelines in docs/STANDARDS.md or team/code-style.txt? Just add the pattern and CodeRabbit will pick it up.

Why it matters

This has huge implications. For one, that means CodeRabbit will follow the same rules you set with your AI coding agent. No more context switching. No more explaining the same standards twice.

It also gives you a way to specify exactly how CodeRabbit should do a PR review and what best practices you want the CodeRabbit review agent to follow. Now, you can just add these guidelines to your rules (be it from Cursor, GitHub, etc.) and:

  • Enforce style and formatting consistency - If your .cursorrules say "use camelCase for functions, PascalCase for components," CodeRabbit will flag violations during review.

  • Maintain architecture patterns - Define your preferred file structure, module boundaries, or dependency rules once and CodeRabbit ensures every PR follows them.

  • Apply team-specific standards - Whether it's "always use early returns" or "prefer composition over inheritance," your unique team preferences become part of every review.

What's next?

CodeRabbit’s not-so-secret magic to PR reviews is the level of context engineering it does. Code Guidelines make CodeRabbit’s reviews even better by adding your coding rules. As for what’s next, I'll give you a hint: context is king. Stay tuned.

If you haven't tried CodeRabbit yet, there's never been a better time. Get started for free and start cutting your code review time (and bugs) in half.