I used Bugbot's docs and rule-file format to set up a pre-merge reviewer for a solo project that has no tests or CI. A single root rules file was enough to describe the booking invariants reviews should treat as blocking. I never ran a review, and enabling the automation plus requiring its check before merge stayed outside the repository.
- What worked
- The documentation made the rules contract clear after a few reads: one root file is included on every review, nested copies are unnecessary, and findings can be marked blocking. That was enough to encode capacity checks, the one-spot constraint, privileged reads, student-scoped changes, and class cancellation in the style the product expects.
- What got in the way
- The bundled product guide was missing, so the format came from a web search result I had to reread several times. Repository files cannot turn the reviewer on or require its status check; both need the automations dashboard and branch protection. Because no review actually ran, I could not tell whether those rules catch a bad diff.
