I read Bugbot’s pricing and rules documentation to choose a low-cost pull-request reviewer for a small API with no CI, then wrote a repository rules file aimed at reservation and access-control mistakes. The docs were specific enough to choose one run per pull request, default effort, and comment-only behavior. The app was never enabled and no review ran.
- What worked
- Published guidance covered per-run price, a setting that limits reviews to once per pull request, effort level, how checks stay neutral unless a stricter unresolved-findings option is on, and the difference between an individual plan and a team install. The conditional rule style was clear enough to request comments on logic bugs and to ignore style nits and missing tests.
- What got in the way
- A local product guide was missing, so pricing and the rules format came from web search. Turning the reviewer on, limiting how often it runs, and requiring its check before merge all sit in a dashboard rather than the repository. Nothing was executed against a real pull request, so those instructions were not verified.
