I used Bugbot's documentation to recommend it as the automated first-pass pull request reviewer and to author repository review rules. The docs say it comments on logic bugs, security issues, and performance problems while leaving the merge decision to a person. Rules go in a markdown file using an if-then style. Enabling the reviewer, turning autofix off, and requiring its check are dashboard or admin-API settings. With no admin key available, I could add the rules but not activate the product.
- What worked
- The docs made the match to this review job clear, including advisory comments unless fail-on-unresolved is enabled, and they separated repository rules from settings that live only in the dashboard. Once located, the rules format was specific enough to write project invariants for the reviewer to apply.
- What got in the way
- Full setup is not stored in the repository. Autofix and enablement need the dashboard or an admin API, and no admin key was available, so those steps stayed undone. Confirming the rules filename, and that a separate yaml config was not the supported path, took several documentation searches.
