Copilot instructions examples

vczh-librariesCopilot instructions

GacUI

vczh-libraries/GacUI/.github/copilot-instructions.md

Control - In these repos we are going to let exceptions blow any libraries, unit tests or test apps up without the needing to recover: - Unless explicitly instructed

homebridgeCopilot instructions

docker-homebridge

homebridge/docker-homebridge/.github/copilot-instructions.md

incorrect. Most development tasks can be accomplished using the documented build scripts and testing procedures below. ## Repository Overview This repository creates the official multi-architecture Docker images for Homebridge

alefragnaniCopilot instructions

vscode-project-manager

alefragnani/vscode-project-manager/.github/copilot-instructions.md

Extension API (Node.js) - Bundler: Webpack with ts-loader - Linting: ESLint (`eslint-config-vscode-ext`) - Testing: Mocha + `@vscode/test-electron` ## Working Effectively Bootstrap and local setup: ```bash git submodule init git submodule update

cloudscape-designCopilot instructions

components

cloudscape-design/components/.github/copilot-instructions.md

prop's type, tightening optional→required, changing an observable default, or altering published test-utils behavior — and prefer deprecation (keep it, mark `@deprecated`, add the replacement) over removal. Additive changes

open-telemetryCopilot instructions

opentelemetry-java-instrumentation

open-telemetry/opentelemetry-java-instrumentation/.github/copilot-instructions.md

changed behavior, not just the edited syntax. Trace relevant callers, configuration, lifecycle, and tests before drawing a conclusion. Report a concrete defect or an explicit repository convention violated

MicrosoftCopilot instructions

vscode-pull-request-github

microsoft/vscode-pull-request-github/.github/copilot-instructions.md

disabled in `tsconfig.base.json` (e.g., `strictNullChecks: false`), but new code should avoid unsafe patterns. - **Testing**: Place tests under `src/test`. Do not include test code in production files. - **Localization**: Use `%key%` syntax

nunitCopilot instructions

nunit

nunit/nunit/.github/copilot-instructions.md

paths) unless explicitly asked to remove them. - Use public Execute(...) entry points for TextRunner tests instead of setting private fields via reflection or forcing parameters directly

fcitxCopilot instructions

fcitx5

fcitx/fcitx5/.github/copilot-instructions.md

Build and test - Configure: `cmake -S . -B build` - Build everything: `cmake --build build` - Build one target: `cmake --build build --target fcitx5` or `cmake --build build --target testemoji` - Run the full

No other project uses it yet

bdringCopilot instructions

FluidNC

bdring/FluidNC/.github/copilot-instructions.md

system/library, `"..."` for local files - **Header Guards**: Use `#pragma once` (not `#ifndef`) ## Build & Test ### Build Targets (PlatformIO) ```bash platformio run --environment wifi # ESP32 + WiFi + WebUI platformio run --environment noradio # ESP32 only

ellisonleaoReads credentialsCopilot instructions

gruvbox.nvim

ellisonleao/gruvbox.nvim/.github/copilot-instructions.md

README.md` - User documentation with installation and configuration examples - `doc/gruvbox.nvim.txt` - Auto-generated Vim help documentation ### Testing Infrastructure - `tests/gruvbox/gruvbox_spec.lua` - Test suite (189 lines) using plenary.nvim - `tests/minimal_init.lua` - Test setup that auto-downloads plenary.nvim

FISCO-BCOSCopilot instructions

FISCO-BCOS

FISCO-BCOS/FISCO-BCOS/.github/copilot-instructions.md

EXECUTOR_TARGET`），以稳定跨模块链接。 - 选项与 vcpkg 特性映射：由 `Options.cmake` 写入 `VCPKG_MANIFEST_FEATURES`（如 `fullnode`、`tests`、`lightnode`、allocator 特性），新增选项应遵循该模式。 ## 关键入口 - 根层：`CMakeLists.txt`、`cmake/Options.cmake`、`cmake/TargetSettings.cmake` 展示模块装配方式 - 框架与契约：`bcos-framework/**`（接口、storage2

MicrosoftCopilot instructions

foundry-local

microsoft/foundry-local/.github/copilot-instructions.md

glob auto-attachment). Keep facts concise and actionable. ## File Hygiene - **Temporary and scratch files** (test logs, coverage reports, build artifacts, diagnostic outputs) must be created inside the build output directory

laude-instituteCopilot instructions

terminal-bench

laude-institute/terminal-bench/.github/copilot-instructions.md

summary of the task instruction and how it implements the solution, and how it tests task completion. Be concise and to the point. Use the following criteria to review

spiffeCopilot instructions

spire

spiffe/spire/.github/copilot-instructions.md

metric rather than conditionally. - Keep `doc/telemetry/telemetry.md` up to date when metrics change, and unit test metrics where reasonable. ## Testing - Prefer fake implementations over generated mocks. Mocks encode specific call patterns

adamhathcockCopilot instructions

sharpcompress

adamhathcock/sharpcompress/.github/copilot-instructions.md

status rtk git status git log -10 rtk git log -10 cargo test rtk cargo test docker ps rtk docker ps kubectl get pods rtk kubectl pods ``` ## Meta commands

No other project uses it yet

eventflowCopilot instructions

EventFlow

eventflow/EventFlow/.github/copilot-instructions.md

patterns when introducing new infrastructure. - Prefer using `EventFlow.TestHelpers` base classes and fixtures when authoring tests so categories, logging, and deterministic IDs behave consistently. ## Build, test, and verification - The solution