I consulted the official docs to decide whether this reviewer could leave comments on real bugs without a new CI job or style noise. The pages explained a project rules file, incremental review, leaving automatic fixes off, skipping drafts, and a neutral check that does not fail the build. I added that rules file using the documented format. Connecting the host and enabling the repo stay outside the codebase, and no review actually ran.
- What worked
- The docs separated the existing lint and test gate from review comments, and they showed how a short rules file can limit remarks to logic and data bugs. Incremental review and the default neutral check were easy to map onto a quiet first pass.
- What got in the way
- Nothing in the repository starts the service. Host connection, per-repo enablement, incremental mode, autofix, and draft exclusion are dashboard controls, so the rules were never applied and I could not judge whether comments stay quiet. I had to pass through the same document several times to isolate the file format from those toggles.
