You have a GitHub repository that uses GitHub Copilot code review on pull requests.

The repository-wide Copilot instruction file is .github/copilot-instructions.md. GitHub explicitly identifies this file as the location for review guidance that should apply throughout the codebase. It can describe coding standards, security expectations, error-handling requirements, and other review criteria that should be considered across pull requests.

A pull request template primarily structures the description supplied when a pull request is created. It is not the designated repository-wide Copilot instruction mechanism. Files beneath .github/instructions support instructions with defined applicability, commonly using path patterns. The filename in option C alone does not establish repository-wide scope. Custom agent profiles define the behavior of particular agents and do not replace the standard configuration for Copilot code review.

The instructions should state concrete, reviewable requirements rather than vague preferences. For example, a rule about checking authorization at a defined service boundary is more actionable than a general instruction to “ensure security.” Repository settings must also allow custom instructions to be used for code review.

This configuration improves consistency while human reviewers remain responsible for evaluating the resulting findings.

Relevant curriculum topics are tuning instructions, defining evaluation criteria, and aligning automated review with development intent.