Drop a CODABAN.md at the root of a repository and the deep review agent reads it before it reviews anything. It is how you turn a general reviewer into one that knows your codebase.
Tell me what you care about and I’ll stop wasting your time on what you don’t.
This page is a stub. The mechanism is live — CODABAN.md is read from the reviewed repository’s root — but the guidance below still needs writing.

​
To write

Draft outline. Replace each item with real content and delete this callout.
  • What it is, versus CLAUDE.md. The deep-review agent reads both. CLAUDE.md describes the codebase for anyone coding in it. CODABAN.md is review-specific — focus, exclusions, tone. Say clearly which belongs where, and what happens when they disagree.
  • A minimal example that earns its place. One short file a reader can paste and immediately benefit from, not an exhaustive template.
  • What to focus on. How to point the reviewer at the parts of the codebase that actually carry risk — auth boundaries, money paths, migrations.
  • What to ignore. Generated code, vendored trees, deliberate patterns that read as smells but aren’t. This is the section that most reduces noise.
  • Tone. How blunt you want the reviewer to be, and where nitpicks are welcome versus unwelcome.
  • Conventions worth stating. Project-specific idioms a general reviewer will otherwise flag every single time.
  • What it can’t do. CODABAN.md shapes the review. It does not grant the agent new capabilities, and it cannot make it run your tests. Name that limit here rather than letting people discover it.
  • Anti-patterns. Files so long the agent’s read budget goes to the config instead of the code. Rules that contradict each other. Instructions that try to suppress whole severities.
  • How to tell it’s working. What changes in the reviews once the file lands, and how to iterate on it.

Reviews

What deep review does with the file once it reads it.

Labels

Per-PR tuning, for when a repo-wide rule is too broad.