Copilot instructions examples

MicrosoftCopilot instructions

WindowsAppSDK

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

Windows App SDK AI contributor guidance

NewFutureCopilot instructions

DDNS

NewFuture/DDNS/.github/copilot-instructions.md

Implement the complete change: code, tests, schema/metadata, Chinese docs, and English docs where applicable. 5. Run focused checks, then the full affected suite. 6. Self-review the diff and continue

clshortfuseCopilot instructions

renodx

clshortfuse/renodx/.github/copilot-instructions.md

find the matching skill and read its `SKILL.md` before acting. When performing a Copilot code review, apply the RenoDX review checklist in `.github/instructions/renodx-code-review.instructions.md` and the review-focused skill in `.github/skills/code-review/SKILL.md

Model Context ProtocolCopilot instructions

csharp-sdk

modelcontextprotocol/csharp-sdk/.github/copilot-instructions.md

signed off on the notes — the published notes then stand as their own reviewed work. Removing it is always the user's decision; never remove it on your own initiative

No other project uses it yet

IvanMurzakCopilot instructions

Unity-MCP

IvanMurzak/Unity-MCP/.github/copilot-instructions.md

library usage, which is an external dependency specifically designed for reflection-based access patterns. ## Code Review Before performing any code review, you **MUST** read the project constitution: [`.specify/memory/constitution.md`](.specify/memory/constitution.md

kstenerudCopilot instructions

KSCrash

kstenerud/KSCrash/.github/copilot-instructions.md

GitHub Copilot Code Review Instructions for KSCrash When performing code reviews on this repository, follow these instructions to identify API breaking changes in the KSCrash crash reporting library. ## Scope

crmneCopilot instructions

ruby_llm

crmne/ruby_llm/.github/copilot-instructions.md

pull request for anything beyond a small fix, so CodeRabbit and GitHub code scanning review it first. Merge your own pull request (squash) once CI is green and those reviews

No other project uses it yet

kubernetes-sigsCopilot instructions

agent-sandbox

kubernetes-sigs/agent-sandbox/.github/copilot-instructions.md

Code Review Guidelines **Project Context & Architecture:** Refer to [AGENTS.md](../AGENTS.md) for full project background, module layout, toolchain versions, and core conventions. **Scope of Review:** Focus strictly on substantive findings tied

No other project uses it yet

CysharpCopilot instructions

MagicOnion

Cysharp/MagicOnion/.github/copilot-instructions.md

Project Custom Instructions ## Coding Review Guidelines When reviewing code, focus on the following points: - Use of Modern C# Features - Consider using the latest syntax available (C# 13 or later), such

wmariussCopilot instructions

awesome-devops

wmariuss/awesome-devops/.github/copilot-instructions.md

list entry with code or workflow changes. - Flag any change to `.github/copilot-instructions.md`, `.github/instructions/`, `AGENTS.md`, `website/scripts/review/` or `.github/workflows/` for maintainer attention. These control automated review and deployment; a contributor adding

MicrosoftCopilot instructions

FLAML

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

reruns-delay 10` for flaky tests ### Coverage - Aim for good test coverage on new code - Coverage reports are generated for Python 3.11 builds - Coverage reports are uploaded to Codecov

No other project uses it yet

LuaLSCopilot instructions

lua-language-server

LuaLS/lua-language-server/.github/copilot-instructions.md

Coding Instructions ## PowerShell 文件编码 - Windows PowerShell 默认编码为 GBK/UTF-16 LE，**严禁**写入项目文件时不指定编码（会导致 UTF8 文件乱码） - `Set-Content`、`Out-File`、`echo >`、`Write-Output >` 等写入操作必须加 `-Encoding UTF8` - 正确示例：`Set-Content -Path file.ts -Value

No other project uses it yet

MicrosoftCopilot instructions

ApplicationInspector

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

Linux, and macOS 5. **Resource cleanup**: Properly dispose of file handles and other resources ## Code Review Checklist Before submitting changes: - [ ] Code builds without errors (`dotnet build`) - [ ] All tests pass (`dotnet

MongoDBCopilot instructions

mongo-python-driver

mongodb/mongo-python-driver/.github/copilot-instructions.md

When reviewing code, focus on: ## Security Critical Issues - Check for hardcoded secrets, API keys, or credentials. - Check for instances of potential method call injection, dynamic code execution, symbol injection

No other project uses it yet

redpanda-dataCopilot instructions

console

redpanda-data/console/.github/copilot-instructions.md

better name or a small extracted function over a paragraph explaining the code. When reviewing, flag added comments that restate the code and suggest deleting them. This is the most

No other project uses it yet

dotnetDeletes or force-pushesCopilot instructions

fsharp

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

After PR is considered ready for review, and especially after it got any code review comments, avoid rewriting git history with rebases etc. Instead prefer merge commits. ## Visual Studio first

posit-devCopilot instructions

positron

posit-dev/positron/.github/copilot-instructions.md

full driver. - Use `npm run valid-layers-check` to check for layering issues ## Coding Guidelines ### Indentation We use tabs, not spaces. ### Naming Conventions - Use PascalCase for `type` names - Use PascalCase

z-libsCopilot instructions

Zen-C

z-libs/Zen-C/.github/copilot-instructions.md

Copilot Instructions These instructions are **MANDATORY** for all code generation and review tasks in the Zen C project. ## 1. Memory Management (Critical) * **Arena Allocation**: The compiler uses a bump-pointer

kubeflowCopilot instructions

pipelines

kubeflow/pipelines/.github/copilot-instructions.md

LLMs. Your job is to help maintain the codebase by being a tier 1 reviewer for incoming PRs. Maintainer time is limited. Your vigilance will help ensure the continuity

xemu-projectCopilot instructions

xemu

xemu-project/xemu/.github/copilot-instructions.md

When performing a code review, consider developer documentation located at `/docs/devel`. Style guide is located at `/docs/devel/style.rst