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.
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
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
overwrite cargo +stable test -p ntex-service --test compile_fail -- --ignored ``` ## Test conventions ### Test documentation Document every test, including ignored and conditionally compiled tests, with rustdoc immediately above its test
Steady6 mentions in 2 weeks
No other project uses it yet
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
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/Microsoft365DSC/.github/copilot-instructions.md
Each resource has a corresponding test file in `Tests/Unit/Microsoft365DSC/`. Its name is `Microsoft365DSC. .Tests.ps1`. - **Documentation:** Resource documentation is in `docs/` and `README.md`. - **External Dependencies:** - PowerShell modules (e.g., `Microsoft.Graph`, `Pester`). - TypeScript
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
PSAppDeployToolkitCopilot instructionsPSAppDeployToolkit/PSAppDeployToolkit/.github/copilot-instructions.md
internal readonly LUID AuthenticationId = AuthenticationId;`). - Separate each field or property from the following XML documentation comment with a blank line. - When a managed NativeMethods wrapper forwards a struct
OPCFoundationCopilot instructionsOPCFoundation/UA-.NETStandard/.github/copilot-instructions.md
integration tests - `tools/` - Source generators, analyzers, and the OPC UA MCP tool - `docs/` - Documentation files - `fuzzing/` - Fuzz targets, corpora, and support scripts ### Build Properties - `Directory.Build.props` - Central build properties - `Directory.Packages.props` - Centralized
touying-typCopilot instructionstouying-typ/touying/.github/copilot-instructions.md
measure`, `layout`, `repeat` - **Text/lists**: `text`, `par`, `list`, `enum`, `item`, `quote`, `raw`, `strong`, `emph` - **Document**: `document`, `page`, `heading`, `outline`, `figure`, `footnote` - **Graphics**: `math`, `rect`, `circle`, `polygon`, `rotate`, `scale`, `fill`, `gradient
dotnetCopilot instructionsdotnet/iot/.github/copilot-instructions.md
DevOps feeds are inaccessible**: Build will fail with "Could not resolve SDK Microsoft.DotNet.Arcade.Sdk" errors. Document this as a known limitation requiring network access to Azure DevOps. ### Alternative Build Approaches When
MicrosoftCopilot instructionsmicrosoft/Olive/.github/copilot-instructions.md
package directory with core functionality - `test/` -- Test suite with requirements-test*.txt files - `docs/` -- Documentation - `.github/workflows/` -- CI/CD pipelines (lint.yml, codeql.yml) - `olive/passes/onnx` -- Directory of ONNX transformations passes - `olive/passes/pytorch` -- Directory of Pytorch
Steady6 mentions in 2 weeks
No other project uses it yet
nelmioCopilot instructionsnelmio/NelmioApiDocBundle/.github/copilot-instructions.md
Contribution Guidelines: Enhanced Follow these mandatory guidelines when contributing code, documentation, and translations to this repository. All contributions will be reviewed for compliance. --- ## General Project Overview * **Project Scope:** This
Steady16 mentions in 2 weeks
No other project uses it yet
gookitCopilot instructionsgookit/goutil/.github/copilot-instructions.md
seconds) - `make csdiff` - Check code formatting issues - `make readme` - Generate README documentation (~0.17 seconds) ### Linting and Quality - `go fmt ./...` - Format code (essential before committing) - `staticcheck ./...` - Run static analysis (has some
Steady7 mentions in 2 weeks
No other project uses it yet
knuckleswtfCopilot instructionsknuckleswtf/scribe/.github/copilot-instructions.md
Copilot Instructions for Scribe ## Project Overview Scribe is a Laravel package that generates API documentation for humans from Laravel codebases. It extracts information from routes, controllers, FormRequests, and other sources
No other project uses it yet
ytsaurusCopilot instructionsytsaurus/ytsaurus/.github/copilot-instructions.md
members/khlebnikov/copilot-instructions ``` ## Additional Resources - Project README: `README.md` - Project ROADMAP: `ROADMAP.md` - Building and testing instructions: `BUILD.md` - Documentation README: `yt/docs/README.md` - C++ style guideline: `yt/styleguide/cpp.md` - Python style guideline: `yt/styleguide/python.md` ## Repository Structure - `util/` - Common utility
themactepCopilot instructionsthemactep/thingino-firmware/.github/copilot-instructions.md
have enough facts, ask user for help. Do not write documentation unless exlicitly asked to. Always test your changes. Write tests when you solve issues to test and confirm
MicrosoftCopilot instructionsmicrosoft/pxt/.github/copilot-instructions.md
semantic versioning for all packages - Maintain backward compatibility when possible - Write clear, self-documenting code with JSDoc comments - Follow the existing code style and patterns in each component ## Architecture Principles
mampfesCopilot instructionsmampfes/hacs_waste_collection_schedule/.github/copilot-instructions.md
python tests/record_fixtures.py ` and commit `tests/fixtures/ /*.json` (or explain a genuine recording blocker). Pipeline source documentation is generated; do not commit `doc/source/ .md`. Follow the [release branch contribution guide](https://github.com
Steady2 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.
