Answer: You customize GitHub Copilot code review by matching customization to your workflow: use .github/copilot-instructions.md for repository-wide review expectations, .github/instructions/**/*.instructions.md for agent-specific and path-specific guidance, and AGENTS.md for repository context such as intentional patterns, architecture boundaries, or review priorities. Status: Confirmed Entry: tool/github-copilot/settings/customize-copilot-review-workflow Revision: 2 Digest: sha256:e6a442b146257df2 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:35:32Z Last changed: 2026-11-17T13:39:19Z (Focus guidance: Keep these files focused on what reviewers need to decide during pull requests. → —) Last verified: 2026-11-20T13:18:27Z Next check: 2026-11-21T13:18:27Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Repository-wide instructions file | .github/copilot-instructions.md | [1] | 2026-11-20 Path-specific instructions file | .github/instructions/**/*.instructions.md | [1] | 2026-11-20 Repository context file | AGENTS.md | [1] | 2026-11-20 Sources: [1] GitHub. "Use GitHub Copilot code review across the pull request lifecycle - GitHub Docs". https://docs.github.com/en/copilot/tutorials/use-copilot-code-review-across-the-pull-request-lifecycle Role: primary. Accessed: 2026-11-20T13:18:27Z Quote: "Use .github/copilot-instructions.md for repository-wide review expectations that should apply to most pull requests." (Supports: Repository-wide instructions file) Quote: "Use .github/instructions/**/*.instructions.md for agent-specific and path-specific guidance when different parts of the codebase have different standards." (Supports: Path-specific instructions file) Quote: "Use AGENTS.md to provide repository context that improves relevance, such as intentional patterns, architecture boundaries, or review priorities." (Supports: Repository context file) Snapshot SHA-256: 7b2c37cb567b0e33a1ead8eb044daa0034852cb705ec1bce7dae4432064222c3 (captured 2026-11-18T13:15:20Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-18T13:15:20Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:18:27Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:18:27Z Last attempt: 2026-11-20T13:18:27Z Notes and limitations: Extracted automatically from a single official source (section "Match customization to your workflow"). Related: https://latestn.com/tool/github-copilot/settings/customize-filesystem-policy How do I customize the filesystem policy for local sandboxing in GitHub Copilot CLI? https://latestn.com/tool/github-copilot/settings/customize-reviews-instructions How do I customize GitHub Copilot code review with custom instructions? https://latestn.com/tool/github-copilot/settings/customize-tabs-cli How do I customize the tabs in GitHub Copilot CLI when browsing issues, pull requests, and gists? https://latestn.com/tool/github-copilot/settings/custom-instructions-support-vscode Which types of custom instructions does GitHub Copilot support in Visual Studio Code? https://latestn.com/tool/github-copilot/settings/customize-cloud-copilot How do I customize GitHub Copilot in the cloud with instructions, tools, and AI models? https://latestn.com/tool/github-copilot/settings/customize-cloud-sandbox How do I customize a GitHub Copilot cloud sandbox session? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-17T13:39:19Z | changed | Focus guidance: Keep these files focused on what reviewers need to decide during pull requests. → — | [1] 2026-11-13T03:35:32Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/settings/customize-copilot-review-workflow/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/github-copilot/settings/customize-copilot-review-workflow POST: https://latestn.com/dispute/tool/github-copilot/settings/customize-copilot-review-workflow with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/settings/customize-copilot-review-workflow?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I customize GitHub Copilot code review to match my team's workflow? Revision 2, last verified 2026-11-20T13:18:27Z. https://latestn.com/tool/github-copilot/settings/customize-copilot-review-workflow (accessed 2026-11-21T09:53:40Z). @misc{LatestN_tool_github_copilot_settings_customize_copilot_review_workflow_r2, title = {How do I customize GitHub Copilot code review to match my team's workflow?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/settings/customize-copilot-review-workflow}}, note = {Revision 2; digest sha256:e6a442b146257df2; last verified 2026-11-20T13:18:27Z; accessed 2026-11-21T09:53:40Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/github-copilot/settings/customize-copilot-review-workflow