Read the docs for automatic Copilot code review and the repository instructions file, then added a repo-wide markdown brief with no frontmatter. The format was specific enough to point reviews at data-integrity and access mistakes. The reviewer was never run: the file is only read from the pull request branch, and automatic review plus approval permission still have to be turned on in account and repository settings.
- What worked
- Documentation distinguished the repo-wide file, which is plain markdown without frontmatter, from path-specific files that need applyTo. That was enough to write a focused review brief and list the three enablement steps in order.
- What got in the way
- The instructions file does not turn review on or count as the required approval. Automatic review, a ruleset request, and permission for Copilot to approve stay in separate settings and were not applied or observed here.