Answer: To write effective custom instructions for GitHub Copilot code review, keep instructions short and focused, use clear structure and formatting, and provide concrete examples. The text recommends limiting any single instruction file to a maximum of about 1,000 lines. Status: Confirmed Entry: tool/github-copilot/features/write-effective-custom-instructions Revision: 3 Digest: sha256:0dc45be749af9984 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:34:19Z Last changed: 2026-11-19T13:10:19Z (directive style: — → Short, imperative directives rather than long narrative paragraphs.) Last verified: 2026-11-20T13:16:40Z Next check: 2026-11-21T13:16:40Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of max instruction file lines | 1,000 lines | lines | [1] | 2026-11-20 core principle | clear, concise, and specific | | [1] | 2026-11-20 structure guidance | Distinct headings that separate different topics. | | [1] | 2026-11-20 directive style | Short, imperative directives rather than long narrative paragraphs. | | [1] | 2026-11-20 examples guidance | Include code snippets showing both correct and incorrect patterns. | | [1] | 2026-11-20 Sources: [1] GitHub. "Using custom instructions to unlock the power of Copilot code review - GitHub Docs". https://docs.github.com/en/copilot/tutorials/customize-code-review Role: primary. Accessed: 2026-11-20T13:16:40Z Quote: "Limit any single instruction file to a maximum of about 1,000 lines." (Supports: max instruction file lines) Quote: "The key to successful custom instructions is to be clear, concise, and specific." (Supports: core principle) Quote: "Distinct headings that separate different topics." (Supports: structure guidance) Quote: "Short, imperative directives rather than long narrative paragraphs." (Supports: directive style) Quote: "Include code snippets showing both correct and incorrect patterns." (Supports: examples guidance) Snapshot SHA-256: 1e3facd4af1fd3f0b5dd24ccb55637b163fc6891c68490eb7c0936410439110e (captured 2026-11-18T13:13:24Z) 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:13:21Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:16:40Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:16:40Z Last attempt: 2026-11-20T13:16:40Z Notes and limitations: Extracted automatically from a single official source (section "Writing effective custom instructions"). Related: https://latestn.com/tool/github-copilot/features/write-integration-tests-copilot How do I write integration tests with GitHub Copilot? https://latestn.com/tool/github-copilot/features/write-unit-tests-copilot-chat How do I write unit tests with GitHub Copilot Chat? https://latestn.com/tool/github-copilot/ide-and-apps/accept-partial-suggestions How do I accept only part of a GitHub Copilot suggestion? https://latestn.com/tool/github-copilot/features/where-to-use-copilot Where can I use GitHub Copilot? https://latestn.com/tool/github-copilot/features/where-to-use-extensions Where can I use extensions with GitHub Copilot? https://latestn.com/tool/github-copilot/features/write-better-prompts How do I write better prompts for GitHub Copilot? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T13:10:19Z | changed | directive style: — → Short, imperative directives rather than long narrative paragraphs. | [1] 2026-11-19T13:10:19Z | changed | structure guidance: — → Distinct headings that separate different topics. | [1] 2026-11-19T13:10:19Z | changed | max instruction file lines: — → 1,000 lines | [1] 2026-11-19T13:10:19Z | changed | examples guidance: Provide concrete examples → Include code snippets showing both correct and incorrect patterns. | [1] 2026-11-19T13:10:19Z | changed | formatting guidance: Use clear structure and formatting → — | [1] 2026-11-19T13:10:19Z | changed | instruction length guidance: Keep instructions short and focused → — | [1] 2026-11-19T13:10:19Z | changed | max lines per instruction file: 1,000 lines → — | [1] 2026-11-17T13:37:03Z | changed | instruction length guidance: — → Keep instructions short and focused | [1] 2026-11-17T13:37:03Z | changed | max lines per instruction file: — → 1,000 lines | [1] 2026-11-17T13:37:03Z | changed | examples guidance: Include code snippets showing both correct and incorrect patterns. → Provide concrete examples | [1] 2026-11-17T13:37:03Z | changed | directive style: Short, imperative directives rather than long narrative paragraphs. → — | [1] 2026-11-17T13:37:03Z | changed | formatting guidance: Distinct headings that separate different topics. → Use clear structure and formatting | [1] 2026-11-17T13:37:03Z | changed | instruction file line limit: about 1,000 lines → — | [1] 2026-11-13T03:34:19Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/features/write-effective-custom-instructions/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/features/write-effective-custom-instructions POST: https://latestn.com/dispute/tool/github-copilot/features/write-effective-custom-instructions with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/features/write-effective-custom-instructions?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I write effective custom instructions for GitHub Copilot code review? Revision 3, last verified 2026-11-20T13:16:40Z. https://latestn.com/tool/github-copilot/features/write-effective-custom-instructions (accessed 2026-11-21T09:52:42Z). @misc{LatestN_tool_github_copilot_features_write_effective_custom_instructions_r3, title = {How do I write effective custom instructions for GitHub Copilot code review?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/features/write-effective-custom-instructions}}, note = {Revision 3; digest sha256:0dc45be749af9984; last verified 2026-11-20T13:16:40Z; accessed 2026-11-21T09:52:42Z} } 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/features/write-effective-custom-instructions