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.
anandnetCopilot instructionsanandnet/Harmony-Music/.github/copilot-instructions.md
patterns when adding new tests - Use Flutter's widget testing framework ## Additional Resources - [Flutter Documentation](https://docs.flutter.dev/) - [GetX Documentation](https://pub.dev/packages/get) - [Hive Documentation](https://docs.hivedb.dev/) - Project README.md
pulumiCopilot instructionspulumi/kubespy/.github/copilot-instructions.md
will fail due to configuration issues ## Common Tasks ### Repository Structure ``` /home/runner/work/kubespy/kubespy/ ├── README.md # Main project documentation ├── CONTRIBUTING.md # Development guidelines ├── Makefile # Build automation ├── go.mod # Go module definition ├── kubespy.go # Main entry point
dotnetCopilot instructionsdotnet/vscode-csharp/.github/copilot-instructions.md
comments over what comments. For complex logic, include references to related files or documentation. Do not remove existing comments unless they are clearly outdated or incorrect. ## Integration Points - **GitHub Copilot
MicrosoftCopilot instructionsmicrosoft/mxc/.github/copilot-instructions.md
platform behavior, feature gates, wire compatibility, and failure semantics. ## Before changing code - Read the documentation for the affected subsystem. Start with the references below rather than inferring behavior from names
stacks-networkCopilot instructionsstacks-network/stacks-core/.github/copilot-instructions.md
Review priorities - Determine the intended behavior from the PR description, changed code, tests, and documentation; comment only when the implementation does not safely establish that behavior. - Prioritize defects with
No other project uses it yet
material-extensionsCopilot instructionsmaterial-extensions/vscode-material-icon-theme/.github/copilot-instructions.md
Follow the project style**: Ensure all changes adhere to the existing code and documentation style. Review the [project's codebase](/) to understand the conventions used. 2. **Use Material Design color
No other project uses it yet
timothystewart6Copilot instructionstimothystewart6/k3s-ansible/.github/copilot-instructions.md
making changes. It is the canonical guide for architecture, safety, implementation, validation, and documentation expectations. Do not duplicate repository guidance here. If instructions need to change, update `AGENTS.md
sonic-netCopilot instructionssonic-net/SONiC/.github/copilot-instructions.md
SONiC (Software for Open Networking in the Cloud) repository — the central hub for project documentation, architecture designs, High Level Design (HLD) documents, roadmaps, governance, and community information. It serves
No other project uses it yet
inspektor-gadgetCopilot instructionsinspektor-gadget/inspektor-gadget/.github/copilot-instructions.md
test/ # Gadget-specific tests README.md # Short description with link to full docs README.mdx # Full documentation in MDX format for the website ``` - `gadget.yaml` defines datasources with field annotations (`columns.width`, `columns.hidden`, `columns.alignment
Steady3 mentions in 2 weeks
No other project uses it yet
OpenMindCopilot instructionsOpenMind/OM1/.github/copilot-instructions.md
table-driven tests where appropriate - Mock external dependencies using interfaces ## Comments - Write clear package documentation - Document exported functions and types - Avoid obvious comments - Use godoc conventions
srl-labsCopilot instructionssrl-labs/containerlab/.github/copilot-instructions.md
directory. - The core library code is located in the `core/` directory. - The documentation files are located in the `docs/` directory. - The constants files are located in the `constants/` directory
Steady5 mentions in 2 weeks
No other project uses it yet
dotnetCopilot instructionsdotnet/macios/.github/copilot-instructions.md
linker, bgen) - `tests/` - Test suites (unit, introspection, extrospection) - `msbuild/` - MSBuild tasks and targets - `docs/` - Documentation and guides - `runtime/` - Runtime components and native code ## Build System This project uses a Make
flightphpCopilot instructionsflightphp/core/.github/copilot-instructions.md
bloating the core library. - Any new features built into the core should be well-documented and tested. - Any new features should be added with a focus on simplicity and performance
arminkCopilot instructionsarmink/FlashDB/.github/copilot-instructions.md
suggest changes** | | `tests/*_tc.c` | utest cases, executed by CI under QEMU | | `docs/` | docsify documentation, `docs/zh-cn` is the Chinese edition | ## Conventions - C99, 4-space indent, no tabs; functions use Allman braces
MicrosoftCopilot instructionsmicrosoft/DirectXTK/.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
dataplatCopilot instructionsdataplat/dbatools/.github/copilot-instructions.md
test file 4. Added new test cases for pattern matching scenarios 5. Updated documentation strings 6. Fixed minor formatting issues ## Detailed Changes by File ### public/Get-DbaDatabase.ps1 - Line 45: Added Pattern parameter
tkemCopilot instructionstkem/cachetools/.github/copilot-instructions.md
work (`test_pickle*`), but the format may change in any release. Do not document, advertise or build on it. - PRs reference an open issue (except trivial fixes), in separate commits
nobiyouCopilot instructionsnobiyou/wx_channel/.github/copilot-instructions.md
config changes take effect immediately. Some require restart or manual handler reload. ## Documentation Resources - **Architecture**: `dev-docs/DOCUMENTATION.md` - **API Endpoints**: `dev-docs/api_documentation.md` - **Fix History**: `dev-docs/FIX_HISTORY.md` (reference
habitat-shCopilot instructionshabitat-sh/habitat/.github/copilot-instructions.md
tests in `tests/` directory - Mock external dependencies - Test both success and failure cases 3. **Documentation**: - Add rustdoc comments for public APIs - Update relevant markdown documentation - Include examples in documentation when
unpollerCopilot instructionsunpoller/unpoller/.github/copilot-instructions.md
Follow existing plugin patterns 2. Keep core library generic 3. Check all errors 4. Document exported functions 5. Write tests in `_test` packages 6. Consider cross-platform compatibility
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.
