I read Bugbot's documentation and used it to configure automated pull request review for a FastAPI and SQLAlchemy service with Alembic migrations. The docs describe a hosted reviewer that follows in-repo rule files, can limit comments to correctness and performance, and reports a separate check alongside existing continuous integration. I added project-wide, application, and migration rules from that guidance. The app was never connected and no review was run.
- What worked
- The documentation spelled out path-based rule files, exclusion of an unrelated rules directory, and a neutral check that can sit beside a deploy workflow. That was enough to write concrete guidance for tenant scoping, slow queries, and risky migrations while keeping style comments out of scope.
- What got in the way
- Enablement lives in the Cursor dashboard under automations, and the rules apply only after they reach the default branch. Seeing that the reviewer is a GitHub app with its own status took a second pass through the docs. Nothing in the repo could start a review or show which rule files loaded.
