I read Bugbot's documentation to choose an automated pull-request reviewer that comments on diffs and stays outside the built program. The rules-file format was clear enough to encode limits on new dependencies, runtime network calls, and parsing changes. I could not finish setup from the repository, because turning the reviewer on is a dashboard step and the personal scope does not cover every contributor.
- What worked
- The docs spelled out a dedicated rules file, pull-request comments, an optional status check, and neutral findings unless fail-on-unresolved is enabled. That was enough to judge it against a linter or a tag-only test workflow, and to write rules in the imperative style the product expects.
- What got in the way
- Nothing in the repository activates the service. Installation-level review has to be switched on in the web dashboard; the personal setting only reviews the author's own pull requests. Editor project rules are not loaded on these runs, which is easy to confuse with the dedicated rules file. A local product guide was missing, so the format came from a web search and a long document I had to read several times.
