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.
zeromicroCopilot instructionszeromicro/go-zero/.github/copilot-instructions.md
milliseconds Optional string `json:",optional"` // Optional field Mode string `json:",default=pro,options=dev|test|rt|pre|pro"` // Validated options } ``` **Service modes**: `dev`/`test`/`rt` disable load shedding and stats
No other project uses it yet
refined-githubCopilot instructionsrefined-github/refined-github/.github/copilot-instructions.md
move, or copy screenshot images or screenshot URLs from any source. - Let tests fail when they require a screenshot; human intervention is needed
No other project uses it yet
getzepCopilot instructionsgetzep/graphiti/.github/copilot-instructions.md
secret, credential, API key, or customer data is in the code or in the tests. - Logging does not include sensitive data: no prompts, no episode content, no credentials. - New behavior
No other project uses it yet
tirth8205Copilot instructionstirth8205/code-review-graph/.github/copilot-instructions.md
graph is cheaper than scanning files and gives you structural context (callers, dependents, test coverage) that file search cannot. ### When to use graph tools FIRST - **Exploring code**: `semantic_search_nodes
1 project uses a version of this
mukul975Copilot instructionsmukul975/Anthropic-Cybersecurity-Skills/.github/copilot-instructions.md
Fraud Impact) | ### Subdomains (Choose One) - **web-application-security** — OWASP, API, web app testing - **network-security** — Network tools, protocols, monitoring - **penetration-testing** — General penetration testing methodology - **red-teaming** — Simulating advanced attackers
No other project uses it yet
layuiCopilot instructionslayui/layui/.github/copilot-instructions.md
源代码开发目录 │ ├── components/ # 组件模块 │ │ ├── button/ │ │ └── ... │ ├── core/ # 核心模块 │ ├── index.js # ESM 打包入口 │ └── index.umd.js # UMD 打包入口 ├── scripts/ # 构建脚本 ├── tests/ # 测试目录 │ ├── unit/ # 单元测试 │ ├── visual/ # 可视化测试示例 └── package.json ``` ### 代码规范 #### Code formatting 采用 Prettier 作为代码格式化工具，使用单引号 `{ "singleQuote": true
No other project uses it yet
sequelizeCopilot instructionssequelize/sequelize/.github/copilot-instructions.md
Workflow ### Essential Commands ```bash # Build specific package node build-packages.mjs core node build-packages.mjs postgres # Run tests by dialect yarn test-integration-postgres yarn test-unit # Start local DBs for testing yarn
No other project uses it yet
The-Art-of-HackingCopilot instructionsThe-Art-of-Hacking/h4cker/.github/copilot-instructions.md
these commands to validate repository state: 1. `lychee --config lychee.toml --no-progress --verbose './README.md'` -- Test core documentation links 2. `cd osint/quick_recon && pip3 install -r requirements.txt` -- Verify Python dependencies
No other project uses it yet
keepassxrebootCopilot instructionskeepassxreboot/keepassxc/.github/copilot-instructions.md
build dir - Formatting (required before commits): - `cmake --build . --target format` (runs clang-format) - Tests: - Run all tests: `ctest -j ` from build dir - Run single test (verbose): `ctest -R -V` - Translations
Steady3 mentions in 2 weeks
No other project uses it yet
python-telegram-botCopilot instructionspython-telegram-bot/python-telegram-bot/.github/copilot-instructions.md
groups required by the project. - `uv run -p 3.14 --all-groups --all-extras --locked tests/` to run tests on a specific Python version. Please use the `-p` flag often
No other project uses it yet
envoyproxyCopilot instructionsenvoyproxy/envoy/.github/copilot-instructions.md
remove it. - **IMPORTANT:** Many bazel targets are very slow/expensive to build/test. Only build or test with bazel when told to, and prefer the narrowest target that covers the change. ## Toolchain
celeryCopilot instructionscelery/celery/.github/copilot-instructions.md
docs; highlight backward-compatibility risks; keep scope focused; encourage consistency and cleanup; optionally suggest tests and local tox usage. - Principles: Very-high confidence or question-first; bottom-line first; avoid
No other project uses it yet
koodo-readerCopilot instructionskoodo-reader/koodo-reader/.github/copilot-instructions.md
channels or window lifecycle is ambiguous - Acknowledge good patterns when you see them ## Testing Standards - Changes to `src/utils/reader/` (live iframe rendering) require manual verification for layout regressions - New IPC handlers
No other project uses it yet
steveyeggeCopilot instructionssteveyegge/beads/.github/copilot-instructions.md
files listed in its routing table. Read those, not this file, for workflow, build, test, and scope rules. The rules most often missed in review: - A PR must close
Steady3 mentions in 2 weeks
1 project uses a version of this
hcengineeringCopilot instructionshcengineering/platform/.github/copilot-instructions.md
parallel ops - Svelte stores for shared state, separate business logic - JSDoc public APIs, tests alongside code - Run `rushx test` before commit ## Avoid ❌ `any` without reason ❌ console.log() ❌ Mixed concerns ❌ Circular deps
Steady4 mentions in 2 weeks
No other project uses it yet
floci-ioCopilot instructionsfloci-io/floci/.github/copilot-instructions.md
except in the files it still suppresses. - Wildcard imports in `src/main`. Static wildcards in tests are fine. - An empty `catch` block. A tolerated exception is logged, or named `ignored
Steady5 mentions in 2 weeks
1 project uses a version of this
MicrosoftCopilot instructionsmicrosoft/winget-cli/.github/copilot-instructions.md
src/PowerShell`) - Microsoft.WinGet.Client and Microsoft.WinGet.Configuration cmdlets - **Configuration system** - DSC-based system configuration using WinGet ## Building, Testing, and Running ### Initial Setup Use a configuration file in `.config` as in `winget configure .config/configuration.winget
BabylonJSCopilot instructionsBabylonJS/Babylon.js/.github/copilot-instructions.md
lint:advisory` (includes warnings omitted by the normal quiet lint commands) - **Unit tests**: `npm run test:unit` ## Code review When reviewing a PR or reviewing changes on the current branch
Steady6 mentions in 2 weeks
No other project uses it yet
daprCopilot instructionsdapr/dapr/.github/copilot-instructions.md
operator/ # Operator proto placement/ # Placement service proto scheduler/ # Scheduler service proto sentry/ # Sentry proto tests/ integration/ # Integration tests (run against real daprd binary) e2e/ # End-to-end tests (require Kubernetes
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/typescript-go/.github/copilot-instructions.md
development takes place in the `internal` directory, and most behaviors can be tested via compiler tests. Most development on the codebase is in Go. Standard Go commands and practices apply
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.
