Copilot instructions examples

zeroc-iceCopilot instructions

ice

zeroc-ice/ice/.github/copilot-instructions.md

branches. Breaking change(s): - [Description of the breaking change] ``` ## Changelog Validation **When reviewing PRs, check if code changes have a changelog fragment under `changelog.d/`.** Changelog entries are added as fragment

MicrosoftCopilot instructions

DirectXTex

microsoft/DirectXTex/.github/copilot-instructions.md

ERROR_FILE_TOO_LARGE)` | | `HRESULT_E_CANNOT_MAKE` | `HRESULT_FROM_WIN32(ERROR_CANNOT_MAKE)` | ## Code Review Instructions When reviewing code, focus on the following aspects: - Adherence to coding standards defined

aagentahCopilot instructions

nw_wrld

aagentah/nw_wrld/.github/copilot-instructions.md

clear regression risk**. - If you are not confident it is must-fix, **stay silent**. #### Review priorities (in order) 1. **Behavior safety** - For valid inputs, changes should

dotnetCopilot instructions

android

dotnet/android/.github/copilot-instructions.md

initialize `TaskEnvironment` to `Fallback` when implementing the interface directly so direct instantiation also works. - Review helpers, exception paths, and static state for thread safety. Do not mutate shared process state

devcontainersCopilot instructions

images

devcontainers/images/.github/copilot-instructions.md

Copilot Code Review - Every image change in a contributor PR requires a manifest bump. For breaking changes such as a base OS change, increment the major component and reset minor

chi111iCopilot instructions

BypassAIGC

chi111i/BypassAIGC/.github/copilot-instructions.md

Copilot Code Review Instructions 请始终使用简体中文进行代码审查。 审查目标不是给出泛泛的风格建议，而是尽早发现会破坏项目的真实问题。优先指出阻塞合并的问题，并按严重程度排序。 ## 审查优先级 优先检查以下问题： - 破坏现有功能、调用链、接口契约或用户流程的改动。 - 前端和后端 API 契约不一致，例如认证方式、请求参数、响应字段、SSE、下载 URL。 - 认证、鉴权、用户隔离、管理员接口、token、卡密兼容逻辑中的安全或兼容性问题。 - 并发控制

oss-review-toolkitCopilot instructions

ort

oss-review-toolkit/ort/.github/copilot-instructions.md

When performing a code review on a pull request, verify the following things: * there is no merge commit among the commits of the pull request, * the commit messages use American

BetterThanTomorrowCopilot instructions

calva

BetterThanTomorrow/calva/.github/copilot-instructions.md

with the REPL API](https://github.com/BetterThanTomorrow/calva/issues/3244)`). * After changing code, run CodeScene's `code_health_review` on the changed files. If Code Health drops, fix the issues, run the review

zereightCopilot instructions

gitlab-mcp

zereight/gitlab-mcp/.github/copilot-instructions.md

Root cause analysis, build fixes | Full access | | @verifier | Evidence-based completion checks | Test runner | | @code-reviewer | Code quality, spec compliance | READ-ONLY | | @security-reviewer | OWASP vulnerability detection | READ-ONLY | | @test

No other project uses it yet

DynamoDSCopilot instructions

Dynamo

DynamoDS/Dynamo/.github/copilot-instructions.md

analyzer warnings for XML-related vulnerabilities (CA2327, CA2329, CA2330, CA2328) are treated as errors - Code changes should contain no files larger than 50 MB (validated by the `check_file_size.yml` workflow) ## Agent

MicrosoftCopilot instructions

maker.js

microsoft/maker.js/.github/copilot-instructions.md

repository. ## Before Committing Always: 1. Review the files being committed with `git status` or `git diff --cached` 2. Ensure only source code, tests, and documentation are included 3. Check that

JurajNyiriCopilot instructions

HomeAssistant-Tapo-Control

JurajNyiri/HomeAssistant-Tapo-Control/.github/copilot-instructions.md

text until they agree. Keep changes small and reviewable. Do not make broad root-cause claims without verifying the current code and relevant dependencies. Disclose AI assistance in PR descriptions

MicrosoftDocsCopilot instructions

architecture-center

MicrosoftDocs/architecture-center/.github/copilot-instructions.md

produced the initial draft with minimal human authorship - `ai-usage: ai-assisted` – Human-directed, reviewed, and edited with AI support - Omit only for markdown that is not related to articles

Microsoft AzureCopilot instructions

azure-functions-host

Azure/azure-functions-host/.github/copilot-instructions.md

General * Make only high-confidence suggestions when reviewing code changes. * Always use the latest version of C#, currently C# 13 features. * Never change global.json unless explicitly asked to. * Never change

igraphCopilot instructions

igraph

igraph/igraph/.github/copilot-instructions.md

Code review guidelines When performing a code review, keep in mind the following. ## Coding standards - Check that all values of integer type are represented as `igraph_int_t`, except

YoastCopilot instructions

wordpress-seo

Yoast/wordpress-seo/.github/copilot-instructions.md

/PULL_REQUEST_TEMPLATE.md). [`AGENTS.md`](../AGENTS.md) adds agent-behaviour guidance. If anything below contradicts these, prefer them. ## Review priorities ### PR hygiene - Every required section of the PR template must have content — no empty

apacheCopilot instructions

trafficserver

apache/trafficserver/.github/copilot-instructions.md

conventions that will not themselves cause CI failures but should still be followed in code reviews. **Formatting Rules:** - **Line length:** 132 characters maximum - **Indentation:** 2 spaces (never tabs) - **Braces:** Linux

No other project uses it yet

MicrosoftCopilot instructions

snmalloc

microsoft/snmalloc/.github/copilot-instructions.md

dependency. - Design code to be easy to change, but do not add extension points or abstractions for hypothetical requirements. ## Change Discipline - Avoid over-engineering and review churn. Preserve names

No other project uses it yet

featbitCopilot instructions

featbit

featbit/featbit/.github/copilot-instructions.md

package.json` as the source of truth for available scripts when implementing changes or reviewing CI. ```sh npm ci npm run dev # Vite development server npm run typecheck # TypeScript checks

QexoCopilot instructions

Qexo

Qexo/Qexo/.github/copilot-instructions.md

When performing a code review, respond in Simplified Chinese