How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
alefragnaniCopilot instructionsalefragnani/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 instructionscloudscape-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
Steady22 mentions in 2 weeks
No other project uses it yet
open-telemetryCopilot instructionsopen-telemetry/opentelemetry-java-instrumentation/.github/copilot-instructions.md
handling, and telemetry under supported library usage. Trace relevant callers, configuration, initialization, registration, and tests rather than reasoning only from edited syntax. Do not add defenses for unsupported hypothetical failures
MicrosoftCopilot instructionsmicrosoft/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
Steady4 mentions in 2 weeks
1 project uses a version of this
MicrosoftCopilot instructionsmicrosoft/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
bdringCopilot instructionsbdring/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
nunitCopilot instructionsnunit/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 instructionsfcitx/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
ellisonleaoReads credentialsCopilot instructionsellisonleao/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 instructionsFISCO-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
spiffeCopilot instructionsspiffe/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
laude-instituteCopilot instructionslaude-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
adamhathcockCopilot instructionsadamhathcock/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 instructionseventflow/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
Microsoft AzureCopilot instructionsAzure/azure-sdk-for-java/.github/copilot-instructions.md
Behavior - Always ensure your solutions prioritize clarity, maintainability, and testability. - Never suggest re-recording tests as a fix to an issue - NEVER turn off any Checkstyle or SpotBugs rules
ntex-rsCopilot instructionsntex-rs/ntex/.github/copilot-instructions.md
FEATURES="ntex/tokio,ntex/cookie,ntex/compress,ntex/openssl,ntex/rustls,ntex/ws" cargo fmt --all -- --check cargo +stable clippy --tests --all --no-default-features --features="$FEATURES" -- -D warnings cargo nextest run --all --no-default-features
Steady6 mentions in 2 weeks
No other project uses it yet
Repository-wide instructions for GitHub Copilot, kept in .github/copilot-instructions.md.
How to build and test, the project's structure, and the conventions Copilot should follow in suggestions and reviews.
No. Copilot's coding agent also reads AGENTS.md, so many projects keep the shared rules there.
Open a file to see its discussion. Reports from people and their agents are coming.
