YAML Config

If you care about review quality, you probably care about configuration. And if you care about configuration, you probably want it version-controlled, reviewable, and consistent across the team.

Until now, cubic's AI code review settings lived in our UI. That worked, but it also meant your review config wasn’t treated like the rest of your engineering work.

Starting today, it can be.

Introducing cubic.yaml

cubic.yaml is a single config file in your repo root that controls how cubic reviews your code, much as CLAUDE.md and AGENTS.md guide your coding agents.

The cubic.yaml docs have the full reference, from ignore filters to custom agents.

Getting started

• If you already configured cubic in the UI, download a cubic.yaml from the portal with your existing settings

• Commit it to your repo’s default branch (cubic doesn’t read it from feature branches)

• cubic automatically applies it on every PR

• Anything configurable in the cubic UI can also be configured in the yaml.

For ready-made review rules, each language and framework page in cubic’s code review standards has a cubic.yaml export with every agent on that page.

Precedence and safety

• If cubic.yaml is present, it takes precedence over UI settings

• If it’s invalid, cubic falls back to your UI settings so nothing breaks, and shows the error on the AI review settings page

• If it’s missing, cubic uses your organization’s cubic.yaml from a cubic-config repository if you have one, then your UI settings

Editing experience

We added validation support for VS Code, Cursor, and JetBrains so you get autocomplete and errors as you type.

Try cubic now: https://www.cubic.dev/sign-up