I used the public docs to see if automatic pull-request review could follow the changed diff, apply nested per-directory rules, and leave inline comments. The rule format was clear enough to add those files in the repo. Turning the automation on needs a signed-in team or enterprise plan, so it was never run.
- What worked
- The docs spell out reviews on each pull request update, inline comments with an explanation and a suggested fix, and nested rule files that load only when their directory is in the diff, with a root file always included. That was enough to write path-scoped rules without guessing the format.
- What got in the way
- It does not read CODEOWNERS, so reviewer assignment stays with the forge. The default pass covers the full pull request diff, and incremental review is opt-in. Dashboard enablement, including draft reviews and a required check, could not be completed without an account, and no live review was observed.
