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.
zeroc-iceCopilot instructionszeroc-ice/ice/.github/copilot-instructions.md
Internal refactoring with no behavioral changes - Test-only, CI/CD, and build system changes - Internal documentation ### Template if missing: ``` This PR has [description], but doesn't add a changelog fragment under
alefragnaniCopilot instructionsalefragnani/vscode-bookmarks/.github/copilot-instructions.md
Controllers**: Multiple controllers manage bookmarks for different workspaces/files - **File Pattern**: `File` class represents a document with its bookmarks - **Bookmark Pattern**: `Bookmark` interface with line and column positions - **Sticky Engine
MicrosoftCopilot instructionsmicrosoft/DirectXTex/.github/copilot-instructions.md
ASCII characters in source files. HLSL files have separate indent/spacing rules defined in `.editorconfig`. - **Documentation**: The project provides documentation in the form of wiki pages available at [Documentation](https://github.com
dotnetCopilot instructionsdotnet/android/.github/copilot-instructions.md
create new commits. The user will squash or fixup as needed. Reference official Android documentation where helpful: * [Android Developer Guide](https://developer.android.com/develop) * [Android API Reference](https://developer.android.com/reference) * [Android
Microsoft AzureCopilot instructionsAzure/AKS/.github/copilot-instructions.md
targeted patterns. --- ## Part 1: Repository Standards ### Repository Overview This repository contains resources, examples, and documentation for the Azure Kubernetes Service (AKS) Engineering team: - **Production Website**: <https://blog.aks.azure.com> (Docusaurus blog
devcontainersCopilot instructionsdevcontainers/images/.github/copilot-instructions.md
sync until release preparation. This restriction applies only to version pins, so unrelated README documentation edits remain valid. - Adding a variant means updating the architecture entry in `manifest.json`, listing
WWBNReads credentialsCopilot instructionsWWBN/AVideo/.github/copilot-instructions.md
conventions - [avideo-prefer-existing-frontend-libraries.instructions.md](instructions/avideo-prefer-existing-frontend-libraries.instructions.md) — reuse bundled libraries - [avideo-reuse-existing-code.instructions.md](instructions/avideo-reuse-existing-code.instructions.md) — search-first workflow and helper inventory ## Documentation Maintenance Before completing any relevant code change in AVideo, the Encoder or its plugins, always
Steady10 mentions in 2 weeks
No other project uses it yet
apacheCopilot instructionsapache/polaris/.github/copilot-instructions.md
stay silent unless the diff gives a concrete reason to believe a high-value documentation, security, or test coverage update may be missing. Only comment when you can name
Steady2 mentions in 2 weeks
No other project uses it yet
LedFxCopilot instructionsLedFx/LedFx/.github/copilot-instructions.md
docs URL 2. Read README in `.venv/Lib/site-packages/ *.dist-info/` 3. Test the exact documented example first 4. Compare your data types/shapes to documented API (e.g., float32 vs float64, array axis
zereightCopilot instructionszereight/gitlab-mcp/.github/copilot-instructions.md
trivial ops, small clarifications, single commands. - Route code to `@executor`. Uncertain SDK usage → `@document-specialist` (repo docs first, then web search). - Route debugging to `@debugger`. Architecture analysis to `@architect`. ## Agent
Steady8 mentions in 2 weeks
No other project uses it yet
DynamoDSCopilot instructionsDynamoDS/Dynamo/.github/copilot-instructions.md
tests) if you want a quicker signal. ## Code Style and Formatting ### Standards, XML Documentation and Analyzers - **Coding Standards**: Follow the [Dynamo Coding Standards](https://github.com/DynamoDS/Dynamo/wiki/Coding-Standards) - **Naming Standards**: Follow
MicrosoftCopilot instructionsmicrosoft/maker.js/.github/copilot-instructions.md
with `git status` or `git diff --cached` 2. Ensure only source code, tests, and documentation are included 3. Check that no build artifacts or lockfiles are being staged for commit
MicrosoftDocsCopilot instructionsMicrosoftDocs/architecture-center/.github/copilot-instructions.md
These instructions define a unified style and process standard for authoring and maintaining learn.microsoft.com documentation with GitHub Copilot or other AI assistance. ## Learn-wide Instructions Below are instructions that apply
actionsCopilot instructionsactions/setup-java/.github/copilot-instructions.md
support, keep the distribution enum, factory, package-capability map, platform-capability map, README support documentation, unit tests, and relevant end-to-end workflow coverage consistent. - Unit tests live under `__tests
Microsoft AzureCopilot instructionsAzure/azure-functions-host/.github/copilot-instructions.md
that XML doc comments are created for any public APIs. When applicable, include ` ` and ` ` documentation in the comments. ### Nullable Reference Types * Declare variables non-nullable, and check for `null
igraphCopilot instructionsigraph/igraph/.github/copilot-instructions.md
reference to a public function is modified, and therefore cannot be `const`, the documentation of that public function should make this clear. Parameters that are passed by value should
MicrosoftCopilot instructionsmicrosoft/msticpy/.github/copilot-instructions.md
pytest markers: `unit`, `integration`, `slow` - **Tools**: `tools/` supplementary tools not core to the package - **Documentation**: `docs/` - Sphinx source files and notebooks ### Key Subpackages - `msticpy/data/` - Data providers and query execution - `msticpy/context
apacheCopilot instructionsapache/trafficserver/.github/copilot-instructions.md
Blocking operations in event threads - ❌ Creating threads manually (use async event system) ### Comments and Documentation **Minimal comments philosophy:** - Only add comments where code isn't self-explanatory - **Don't** describe
Steady5 mentions in 2 weeks
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/snmalloc/.github/copilot-instructions.md
src/snmalloc/stl/`. - Prefer explicit wiring and conversions over hidden dependencies or convention-based behaviour. - Document behavioural coupling at the component whose modification could break the dependency. - Design code to be easy
No other project uses it yet
crazywhaleccCopilot instructionscrazywhalecc/static-php-cli/.github/copilot-instructions.md
build, download, doctor, shell, terminal, CI, smoke-test, or log failures. - `.agents/skills/staticphp-documentation-sync`: synchronize bilingual documentation (`docs/en/` and `docs/zh/`) when features, commands, configuration, APIs, or behavior change. ## Quick Reference - **Entrypoint
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.
