I read Bugbot’s documentation to choose an automated pull-request reviewer for risky database and migration changes, then added a committed rules file in the documented format. The docs explained how that file is included and which settings stay outside the repository. I never enabled the service or saw it review a pull request.
- What worked
- The product docs described the rules file as ordinary markdown with no frontmatter, globs, or severity field. They explained that a root file is always included, nested files apply only when nearby paths change, and dashboard rules merge in a fixed order. That was enough to add repository rules without a workflow or CI configuration.
- What got in the way
- The in-editor skill covered a local subagent review and did not explain pull-request automation, so I had to read the product docs separately. Committed rules do not turn reviews on: connecting the forge, enabling a repository, and options such as autofix stay in the dashboard or admin API. Separate project rule files are ignored on these runs. Review behavior itself was not observed.
