Copilot instructions examples

ExcelDataReaderCopilot instructions

ExcelDataReader

ExcelDataReader/ExcelDataReader/.github/copilot-instructions.md

cell values. Do not implicitly change `GetValue()` or `AsDataSet()` output when adding metadata accessors. ## Tests and fixtures - Put shared spreadsheet behavior in `src\ExcelDataReader.Tests\ExcelTestBase.cs` and OpenXML-only shared behavior

MicrosoftCopilot instructions

FLAML

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

autogen code (note: AutoGen has moved to a separate repository) - `flaml/fabric/`: Microsoft Fabric integration - `test/`: Comprehensive test suite ## Build and Test Commands ### Installation ```bash # Basic installation pip install -e . # Install

No other project uses it yet

LuaLSCopilot instructions

lua-language-server

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

兜底 ## 长耗时命令轮询 - 后台运行的长时间命令（如 `test.lua` 完整测试、`build-doc.lua`）**不会自动通知完成**，必须主动轮询结果文件确认 - 完整测试：检查 `temp/test_full*.log` 是否出现 `test finish.`（无 error 即通过；full 阶段耗时较长，需多次轮询） - build-doc：检查退出码 `DOC=0` - 轮询方式：读取日志文件末尾或 `grep

No other project uses it yet

hzellerCopilot instructions

rpi-rgb-led-matrix

hzeller/rpi-rgb-led-matrix/.github/copilot-instructions.md

with elevated privileges unless the user explicitly requests execution. For initial Pi 2 runtime testing, suggest `--led-slowdown-gpio=1` rather than forcing a compile-time setting

No other project uses it yet

MicrosoftCopilot instructions

ApplicationInspector

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

executables; aims to support all currently supported .NET versions) - **Build System**: dotnet CLI - **Test Framework**: xUnit - **Solution Structure**: Multi-project .NET solution with 7 projects - **Rule Format**: JSON files following

sshnetCopilot instructions

SSH.NET

sshnet/SSH.NET/.github/copilot-instructions.md

Cryptography | BouncyCastle (`BouncyCastle.Cryptography`) | | Logging | `Microsoft.Extensions.Logging.Abstractions` (`ILogger`/`ILoggerFactory`) | | Testing | MSTest v4, Moq, Testcontainers (Docker for integration tests) | | Build tooling | .NET SDK 10.0.100, Nerdbank.GitVersioning | | Static analysis | StyleCop.Analyzers, Meziantou.Analyzer, SonarAnalyzer.CSharp | --- ## Code organization ``` src/Renci.SshNet

No other project uses it yet

MongoDBCopilot instructions

mongo-python-driver

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

Sphinx format. ## PyMongo-specific Concerns - Do not review files within `pymongo/synchronous` or files in `test/` that also have a file of the same name in `test/asynchronous` unless the reviewed changes

No other project uses it yet

nyldnCopilot instructions

claude-octopus

nyldn/claude-octopus/.github/copilot-instructions.md

Shell scripts use `set -euo pipefail` and bash 3.x compatibility (no associative arrays) - Tests are in `tests/unit/` using a custom `test-framework.sh` (test_case/test_pass/test_fail) - All provider detection is graceful — missing

No other project uses it yet

redpanda-dataCopilot instructions

console

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

wire-compatible, hook signature changes, API version placement, generated output not regenerated. 4. **Tests.** New behavior needs a test. Backend prefers table-driven with `t.Run`; frontend splits `.test.ts` (unit, node

No other project uses it yet

dotnetDeletes or force-pushesCopilot instructions

fsharp

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

binlog-mcp` MCP (structured errors, root-cause diagnose, MSBuild perf X-ray). ## Test Default: `-c Debug` Use `-c Release` for: EmittedIL tests, Optimizer tests, full component runs spot check: `dotnet

posit-devCopilot instructions

positron

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

organized into key architectural layers: ### Root Folders - `src/`: Main TypeScript source code with tests in `src/vs/*/test/` folders (Vitest `.vitest.ts`/`.vitest.tsx` and Mocha `.test.ts`) - `build/`: Build scripts and CI/CD tools

zenc-langCopilot instructions

zenc

zenc-lang/zenc/.github/copilot-instructions.md

Standard Library**: * Import with `import "std/io.zc"`, `import "std/vec.zc"`. * Use `println "msg"` (shorthand) or `printf`. * **Testing**: * Use `test "name" { ... }` blocks for unit tests

EasyCorpCopilot instructions

EasyAdminBundle

EasyCorp/EasyAdminBundle/.github/copilot-instructions.md

assets` to recompile assets whenever you make any change in assets/ directory - Run `make tests` (or `./vendor/bin/phpunit`) to run PHPUnit tests - Run `./vendor/bin/phpstan analyse` to run PHPStan checks - Run `yarn

No other project uses it yet

kubeflowCopilot instructions

pipelines

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

names are descriptive and meaningful. - Make sure that new logic is covered by unit tests. - Make sure that large changes have adequate large tests, not just small tests. - Make sure

arcboxlabsCopilot instructions

arcbox

arcboxlabs/arcbox/.github/copilot-instructions.md

require code signing:** ```bash codesign --entitlements bundle/arcbox.entitlements --force -s - arcbox-daemon ``` Required for: examples, tests touching hypervisor. See [arcbox.entitlements](bundle/arcbox.entitlements) - `mode_t` types (e.g., `libc::S_IFMT`) are `u16` (Linux

solvespaceCopilot instructions

solvespace

solvespace/solvespace/.github/copilot-instructions.md

Simplicity**: Does a pull request add unnecessary complexity, or add unwanted dependencies? 3. **Human Testing**: Is there evidence that a human built the new code and actually tried it? They

fwupdCopilot instructions

fwupd

fwupd/fwupd/.github/copilot-instructions.md

build-fwupd` (in venv) -- takes 45+ minutes. NEVER CANCEL. Set timeout to 60+ minutes. - Test command: `test-fwupd` (in venv) -- takes 15+ minutes. NEVER CANCEL. Set timeout to 30+ minutes

MicrosoftCopilot instructions

apm

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

Lint` job runs (see `.github/workflows/ci.yml`): 1. `uv run --extra dev ruff check src/ tests/` 2. `uv run --extra dev ruff format --check src/ tests/` 3. YAML I/O safety guard (rejects

getwudCopilot instructions

wud

getwud/wud/.github/copilot-instructions.md

Frontend): Vue 3, Vuetify 3, TypeScript, Iconify (`@iconify/vue`). - `e2e/` (Backend E2E): Cucumber / Gherkin test suite. - `ui-e2e/` (Frontend E2E): Playwright test suite. - `website/` (Documentation): Docusaurus site. 2. **Validation & Configuration**: - Always

f4exbCopilot instructions

sdrangel

f4exb/sdrangel/.github/copilot-instructions.md

those to installed dependencies or use Docker (there is a separate `sdrangel-docker` project). - Tests & verification - There are no central unit-test runners in the top-level; run small tests