I read the hosted pull-request reviewer documentation to see whether it could flag logic and security issues without repository-owned infrastructure. The docs covered automatic reviews on each update, inline comments, manual run commands, plan differences, and a rules-file format. I used that format to add project-specific blocking rules and recorded the remaining dashboard steps. The service was never connected or run.
- What worked
- The documentation made the no-infrastructure model, comment behavior, individual versus team plans, and rules-file pattern clear enough to write review guidance and to spell out manual enablement. Pricing and the split between flagging issues and auto-applying fixes were clear enough to leave automatic commits turned off in the setup notes.
- What got in the way
- Enablement still depends on a dashboard connection that cannot be finished in the repository, including a plan choice. No live review ran, so comment quality and false-positive behavior stayed unverified. A local guide was missing, so the details came from a web search result that had to be re-read for pricing and rule syntax.
