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.
intelCopilot instructionsintel/neural-compressor/.github/copilot-instructions.md
Applies to all Python files except `examples/`, `neural_compressor/torch/algorithms/fp8_quant/`, and `test/torch/`. ## Docstring examples in documentation – blacken-docs - Code blocks inside Markdown and reStructuredText documentation files must also follow **black** formatting
dvorkaCopilot instructionsdvorka/mindforger/.github/copilot-instructions.md
Copilot instructions This document provides instructions to the copilot AI assistants for dvorka/mindforger project. ## General instructions - Always write beautiful, readable, and maintainable code. - Handle errors, exceptions, and corner cases. - Prefer
nteractCopilot instructionsnteract/semiotic/.github/copilot-instructions.md
high-level API does not expose. - Keep public APIs, types, chart specs, schemas, generated documentation, and focused tests synchronized. - Do not hand-edit build output or generated marker sections
CommunityToolkitCopilot instructionsCommunityToolkit/Maui/.github/copilot-instructions.md
Overview This document provides guidelines for using GitHub Copilot to contribute to the .NET MAUI Community Toolkit. It includes instructions on setting up your environment, writing code, and following best
pjsipCopilot instructionspjsip/pjproject/.github/copilot-instructions.md
configuration - ICE/NAT: `pjnath/include/pjnath/ice_strmtp.h` - Call handling: `pjsip/src/pjsua-lib/pjsua_call.c` - Transport: `pjsip/include/pjsip/sip_transport.h` ## Coding Conventions Follow: https://docs.pjsip.org/en/latest/get-started/coding-style.html Documentation source (for when the docs site is not directly accessible): https://github.com/pjsip/pjproject_docs ### Essentials - **ANSI
No other project uses it yet
rust-crossCopilot instructionsrust-cross/cargo-zigbuild/.github/copilot-instructions.md
pass (tests on Ubuntu, macOS, and Windows with multiple Rust and zig versions) - Update documentation in README.md if adding new features or changing behavior ### Testing Strategy - The CI tests
Steady24 mentions in 2 weeks
No other project uses it yet
vczh-librariesCopilot instructionsvczh-libraries/GacUI/.github/copilot-instructions.md
found in `REPO-ROOT/Project.md`. - Following `Leveraging the Knowledge Base`, find the knowledge and documents for this project in `REPO-ROOT/.github/KnowledgeBase/Index.md`. - Before writing to a source file, read
pt-pluginsCopilot instructionspt-plugins/PT-depiler/.github/copilot-instructions.md
every visited page pays for them. - **Options page** — `options/`: the Vue 3 SPA. - **Offscreen document** — `offscreen/`: owns IndexedDB and the scanning / social helpers; background and options reach it over messages
flexpilot-aiCopilot instructionsflexpilot-ai/flexpilot-ide/.github/copilot-instructions.md
types they occur on but in the best matching namespace. For instance, document changes aren't sent by a document but via the `workspace.onDidChangeTextDocument` event. The event will contain
homebridgeCopilot instructionshomebridge/docker-homebridge/.github/copilot-instructions.md
information here is incomplete or 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
cloudscape-designCopilot instructionscloudscape-design/components/.github/copilot-instructions.md
cite the rule and say why. These are the repo's house conventions. ## Comments & documentation - Comment only the non-obvious WHY (why a warning is suppressed, why a workaround exists
open-telemetryCopilot instructionsopen-telemetry/opentelemetry-java-instrumentation/.github/copilot-instructions.md
changed public Java API, identify the *publishing artifact* before claiming a break. Symbols explicitly documented as internal, unsupported, and subject to change are not supported public APIs merely because their
ellisonleaoReads credentialsCopilot instructionsellisonleao/gruvbox.nvim/.github/copilot-instructions.md
containing all colorscheme logic - `colors/gruvbox.lua` - Simple loader that calls `require("gruvbox").load()` - `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
spiffeCopilot instructionsspiffe/spire/.github/copilot-instructions.md
server's CA, warrant extra scrutiny. ## Compatibility guarantees SPIRE makes strong compatibility promises documented in `doc/upgrading.md`. Treat a violation of these as a blocking issue. - **Server-to-server version skew
CheckmkCopilot instructionsCheckmk/checkmk/.github/copilot-instructions.md
Copilot instructions for check_mk Project conventions are documented in `CLAUDE.md` at the repository root — apply those when suggesting changes. ## AI tooling lives elsewhere Reusable AI workflows for this project
Steady7 mentions in 2 weeks
No other project uses it yet
eventflowCopilot instructionseventflow/EventFlow/.github/copilot-instructions.md
jobs live under `Source/EventFlow/Sagas` and `Source/EventFlow/Jobs`, coordinating cross-aggregate workflows and deferred execution. - Documentation that explains the concepts is checked in under `Documentation/`; updates should travel with code changes. ## Extension
Microsoft AzureCopilot instructionsAzure/azure-sdk-for-java/.github/copilot-instructions.md
verify that your changes are correct, including any relevant tests or documentation checks. - Always ask for clarifications if the request is ambiguous or lacks sufficient context. - Always provide detailed justifications
ntex-rsCopilot instructionsntex-rs/ntex/.github/copilot-instructions.md
Repository instructions ## Test conventions ### Test documentation Document every test, including ignored and conditionally compiled tests, with rustdoc immediately above its test attributes: ```rust /// STATEMENT: A retired service is rebound rather
BrighterCommandCopilot instructionsBrighterCommand/Brighter/.github/copilot-instructions.md
should follow the guidelines in the [CONTRIBUTING.md](../CONTRIBUTING.md) file. These guidelines derive from that document. ## Detailed Instructions For comprehensive guidance on working with this codebase, Copilot should read the following
omryCopilot instructionsomry/omegaconf/.github/copilot-instructions.md
call out only actionable gaps, especially: - missing or insufficient tests for code changes; - missing documentation updates for API or behavior changes; - missing news fragments for non-trivial user-visible changes
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.
