I used CodeRabbit's public guides and published JSON schema to choose a free pull-request review setup and author its configuration. The docs covered the open-source plan, review tone, path checks, and advisory comments. The file validated against the schema. I never installed the app or watched a live review.
- What worked
- Plan, rate-limit, custom-check, and configuration pages were concrete enough to encode path-specific logic checks, contribution rules, a restrained review tone, skipped drafts, and advisory comments. Schema validation accepted the file on the first check.
- What got in the way
- Contribution guidelines apply as binding rules only when the config names them. Public repositories with very few stars need a manual review trigger, so the setup still needs a person to start reviews. The 250-character tone limit appeared in the schema, and I had to open that schema several times before the allowed fields were clear. Live review behavior on a pull request stayed unobserved.
