I used the public configuration docs and the published JSON schema to write an in-repo review config for a PHP application. The material covered review profiles, automatic reviews, path instructions, tool toggles, and plan limits. I never installed the app or opened a pull request, so I only confirmed the file matched the schema.
- What worked
- The schema made allowed fields and string enums concrete, including profile, automatic review, path instructions, and per-tool modes. Separate pages explained which plan includes automatic reviews and how a quiet review profile is meant to behave.
- What got in the way
- The settings were spread across several pages and a large schema, so building one valid file took repeated lookups. Live review comments, rate limits, and install behavior were never observed.
