One CodeRabbit configuration for every code repo of the Advanced Telerobotics Research Laboratory, so lab members get reviews that follow the lab's dev guidelines without adding a config file to their projects.
_{Advanced Telerobotics Research Laboratory · Department of Computer Science · Kent State University}

Start here

How it works Why every lab repo gets these settings with nothing to install.	What reviews check Which dev-guidelines page applies to which files.	Who can approve What lab members can do on their own pull requests, and what outside contributors cannot.
The config file .coderabbit.config.ts, the only file CodeRabbit reads here.	Changing the config Edit, type-check and open a pull request.	Per-repo exceptions Override a few settings in one repo and keep the rest.

How it works

CodeRabbit treats a repository named coderabbit as the central configuration for its organization. .coderabbit.config.ts here applies to every ATR-Lab repo that has no CodeRabbit config of its own. The CodeRabbit app is installed on all ATR-Lab repositories, so a new repo is covered from its first pull request.

The setup follows pingdotgg/t3code's config, with the lab's dev guidelines in place of T3 Code's internal docs. Reviews are kept quiet:

• Automatic reviews run on every pull request that is not a draft and again on each new push.
• There is no high-level summary, status message, poem or docstring requirement; the profile is "chill".
• Auto-approval is off, because Macroscope handles approvals.
• Build output and caches are skipped: build/, install/, log/, Unity Library/, node_modules/, .venv/ and .pio/.

What reviews check

CodeRabbit loads each page below from ATR-Lab/dev-guidelines as a code guideline and holds changed files to it. Updating a page there updates reviews in every lab repo.

Guide	Applies to
Python	*.py
C and C++	*.c, *.cc, *.cpp, *.cxx, *.h, *.hh, *.hpp, *.hxx
JavaScript and TypeScript	*.js, *.jsx, *.mjs, *.cjs, *.ts, *.tsx
Swift	*.swift
Kotlin	*.kt, *.kts
C# and Unity	*.cs
Other languages	Arduino *.ino, Java, MATLAB *.m, Solidity and Ada
ROS 2 packages	package.xml, CMakeLists.txt, setup.py, setup.cfg, launch/ and config/*.yaml
Hardware and firmware	platformio.ini, firmware/, cad/ and bom/
Documentation	README.md, AGENTS.md, CLAUDE.md and CHANGELOG.md

Who can approve

CodeRabbit reads the pull request author's association with the repo, the same way T3 Code's config does.

Author	@coderabbitai approve on their own pull request	Overriding a failed pre-merge check
Owner, member or collaborator	Allowed	CodeRabbit's default rules
Outside or first-time contributor	Someone else must run it	Requested reviewers only

Changing the config

1. Edit .coderabbit.config.ts. Do not add a .coderabbit.yaml here: if both files exist, CodeRabbit uses the YAML and ignores the TypeScript file.

2. Type-check it. The types come from CodeRabbit's config schema:

   npm install
   npm run typecheck

3. Open a pull request. The change applies to every lab repo once it merges to main.

Per-repo exceptions

A repo that adds its own .coderabbit.yaml or .coderabbit.config.ts replaces this config entirely. To keep these settings and change only a few, start that file with inheritance: true.

Repo map

Path	What it holds	Read it when
.coderabbit.config.ts	The central CodeRabbit config	You want to see or change what reviews do
package.json, tsconfig.json	The CodeRabbit config SDK and the type-check script	You change the config
.github/assets/	The README header and icons	You restyle this page
LICENSE	The MIT License for this repo	You reuse the config elsewhere
AGENTS.md	Instructions for coding agents (CLAUDE.md points to it)	You are, or you are directing, a coding agent

Contributing

Suggest a change by opening an issue or a pull request. Changes here reach every lab repo, so say why in the pull request and run the type-check first. To change what reviews hold code to, edit the guide in dev-guidelines instead.

License

The configuration and docs in this repository are released under the MIT License. The names and logos of the Advanced Telerobotics Research Laboratory and Kent State University are trademarks and are not covered by that license.

---

_{ATR Lab docs · About the lab · Getting started · Dev guidelines · All things ROS 2 · All repositories
Advanced Telerobotics Research Laboratory · Department of Computer Science · Kent State University · www.atr.cs.kent.edu}