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.
citusdataCopilot instructionscitusdata/citus/.github/copilot-instructions.md
normal contribution conventions: see `CONTRIBUTING.md` for build/style/PR rules and `src/test/regress/README.md` for the regression-test workflow. ## Agent skills This repo ships task-specific **agent skills** under `.github/skills/`. Before starting a task
Steady3 mentions in 2 weeks
No other project uses it yet
Z3ProverCopilot instructionsZ3Prover/z3/.github/copilot-instructions.md
code generation scripts) - C++20 capable compiler (g++ or clang++) - Git (for version information) ### Test the Repository - Build unit tests: `cmake --build build --target test-z3 --parallel $(nproc)` -- takes
No other project uses it yet
ChainlitCopilot instructionsChainlit/chainlit/.github/copilot-instructions.md
unexpected information that does not match the info here. ## Working Effectively ### Bootstrap, Build, and Test the Repository **CRITICAL**: All commands must complete - NEVER CANCEL any build or test operations
No other project uses it yet
Heroic-Games-LauncherCopilot instructionsHeroic-Games-Launcher/HeroicGamesLauncher/.github/copilot-instructions.md
mode with HMR ```` - **Type-check**: `pnpm codecheck` (runs `tsc --noEmit`) - **Lint**: `pnpm lint` - **Unit tests**: `pnpm test` (Jest, ts-jest). Tests live in `__tests__/` folders alongside source. - **E2E tests**: `pnpm
No other project uses it yet
RT-ThreadCopilot instructionsRT-Thread/rt-thread/.github/copilot-instructions.md
memory alignment / 使用内存对齐 2. **Verify on real hardware or at least QEMU** / **尽可能在真实硬件上验证，或至少在QEMU上验证** - Test on actual hardware when available / 有条件时在真实硬件上测试 - Use QEMU simulation as minimum verification / 至少使用QEMU仿真进行验证 - Consider various
No other project uses it yet
StarRocksCopilot instructionsStarRocks/starrocks/.github/copilot-instructions.md
query planning, metadata management, and coordination - **Java Extensions**: Java - External connectors and UDF framework - **Testing**: Python - Integration tests and SQL test framework ## Architecture Components ### Backend (be/) - C++ The core analytical
aureuserpCopilot instructionsaureuserp/aureuserp/.github/copilot-instructions.md
writing a new one. ## Verification Scripts - Do not create verification scripts or tinker when tests cover that functionality and prove it works. Unit and feature tests are more important. ## Application
No other project uses it yet
mesheryCopilot instructionsmeshery/meshery/.github/copilot-instructions.md
golangci-lint for linting (see `.golangci.yml`) - Error handling should use MeshKit's error utilities - Tests use Go's standard testing library ### JavaScript/React Code - ESLint with Prettier for formatting (see `ui/.eslintrc.js
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/garnet/.github/copilot-instructions.md
unified single-store** design — see the Architecture section below for the current model. ## Build, Test, and Lint ```bash # Build the entire solution dotnet build # Run all Garnet tests dotnet test
Steady9 mentions in 2 weeks
No other project uses it yet
OpenRefineCopilot instructionsOpenRefine/OpenRefine/.github/copilot-instructions.md
Maven build. ## Repository Structure - **main/** – Core application: Java source (`src/main/java`), web application (`webapp/`), and tests (`src/test/java`, `tests/cypress/`) - **modules/grel/** – GREL expression language module - **modules/core/** – Core module (shared code) - **extensions/** – Optional extensions
No other project uses it yet
nasaCopilot instructionsnasa/fprime/.github/copilot-instructions.md
Prime Copilot Instructions General repository guidance — layout, build and test commands, coding conventions, and available skills — is in [`AGENTS.md`](../AGENTS.md) at the repository root. When reviewing a pull request, invoke
Steady5 mentions in 2 weeks
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/presidio/.github/copilot-instructions.md
recognizers`). - Registry and provider patterns exist to decouple components — bypassing them creates hidden dependencies. - Test the complete integration path (unit, integration, and e2e), not just isolated components. ## Security & Privacy Always
is-a-devCopilot instructionsis-a-dev/register/.github/copilot-instructions.md
Follow these instructions on every PR review. This ensures full consistency with the automated tests in `/tests`, the reserved/trusted lists, and maintainer expectations
No other project uses it yet
korniaCopilot instructionskornia/kornia/.github/copilot-instructions.md
torch.compile` behavior where applicable; - use `BaseTester`, injected `device`/`dtype` fixtures, and `self.assert_close()` in tests; - treat half precision, CUDA, MPS, and ONNX as explicit compatibility surfaces; - run focused checks
No other project uses it yet
apereoCopilot instructionsapereo/cas/.github/copilot-instructions.md
application modules (Tomcat, Jetty, etc.) docs/ → Documentation and user guides ci/ → CI scripts and test helpers style/ → Checkstyle, SpotBugs, ErrorProne configs ``` **Key principle**: `api/` modules define contracts, `core/` implements them
No other project uses it yet
misskey-devReads credentialsCopilot instructionsmisskey-dev/misskey/.github/copilot-instructions.md
へ送信しない ## 変更を出す前の最低チェック 1. ESLint 対象の変更ファイルへ package root から `eslint --quiet` を最後に 1 回実行し、実装変更には最も近い test を選んで実行する。 package / repo 全体 lint と広域 test は任意 2. backend で `meta` / `paramDef` / `res` を変更した
No other project uses it yet
BrasilAPICopilot instructionsBrasilAPI/BrasilAPI/.github/copilot-instructions.md
precisar mudar a estrutura, crie uma nova versão (v2, v3, etc.) - Valide com testes E2E antes de fazer merge ### 2. Documentação Sempre Atualizada - **SEMPRE** atualize a documentação OpenAPI ao modificar
No other project uses it yet
gui-csCopilot instructionsgui-cs/Terminal.Gui/.github/copilot-instructions.md
view.Bounds` | `view.Viewport` | | `new RadioGroup (...)` | `new OptionSelector { ... }` | | `Application.RequestStop ()` | `App!.RequestStop ()` (from inside a `Runnable`) | --- ## Build & Test Run all commands from repository root. ```bash # Restore + build dotnet restore dotnet build --no-restore
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/winget-pkgs/.github/copilot-instructions.md
template, keep the change to exactly one package, and summarize validation performed. ## Validation and Testing Commands Validate a manifest locally: ```powershell winget validate --manifest ``` Test installation locally: ```powershell winget settings
No other project uses it yet
data-privacy-stackCopilot instructionsdata-privacy-stack/presidio/.github/copilot-instructions.md
recognizers`). - Registry and provider patterns exist to decouple components — bypassing them creates hidden dependencies. - Test the complete integration path (unit, integration, and e2e), not just isolated components. ## Security & Privacy Always
1 project uses a version of this
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.
