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.
inspecCopilot instructionsinspec/inspec/.github/copilot-instructions.md
GitHub Copilot Instructions for InSpec ## Project Overview InSpec is an open-source infrastructure testing framework written in Ruby. It provides a domain-specific language (DSL) for describing security and compliance
anandnetCopilot instructionsanandnet/Harmony-Music/.github/copilot-instructions.md
Building ```bash # Android flutter build apk # Windows flutter build windows # Linux flutter build linux ``` ### Testing ```bash flutter test ``` ## Coding Guidelines 1. **Follow Dart/Flutter best practices**: - Use `flutter_lints` package rules
pulumiCopilot instructionspulumi/kubespy/.github/copilot-instructions.md
minutes. - **Install the application:** - `make install` -- installs to $GOPATH/bin, takes ~5 seconds. ### Testing - **Run tests:** - `make test_all` -- runs all tests (takes ~13 seconds first time, <1 second subsequent runs
dotnetCopilot instructionsdotnet/vscode-csharp/.github/copilot-instructions.md
CONTRIBUTING.md`). ## Developer Workflows - **Build**: `npm run compile` (or use VS Code build task) - **Test**: `npm test` (runs Jest tests) - **Package**: `npm run package` (creates VSIX) - **Dependencies**: Use `npm run installDependencies
MicrosoftCopilot instructionsmicrosoft/mxc/.github/copilot-instructions.md
from names. - Follow any matching file-scoped instructions under `.github/instructions/`. - Inspect nearby code and tests before editing. Reuse existing abstractions and error types. - Do not hand-edit generated files
stacks-networkCopilot instructionsstacks-network/stacks-core/.github/copilot-instructions.md
changed behavior. ## 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
No other project uses it yet
Shelf-nuReads credentialsCopilot instructionsShelf-nu/shelf.nu/.github/copilot-instructions.md
webapp:dev # Timeout: Set 10+ minutes for startup. Server runs on https://localhost:3000 ``` ### Testing Commands **NEVER CANCEL** test commands. Set appropriate timeouts: ```bash # Unit tests (10+ seconds, NEVER CANCEL
material-extensionsCopilot instructionsmaterial-extensions/vscode-material-icon-theme/.github/copilot-instructions.md
Document your code thoroughly and ensure it is easy to understand and maintain. 6. **Test your changes**: Always test your changes to ensure they do not break existing functionality
No other project uses it yet
filecoin-projectCopilot instructionsfilecoin-project/lotus/.github/copilot-instructions.md
changed behaviour, not the repository in the abstract. Inspect relevant callers, interfaces and tests before commenting. Prioritise, in order: 1. Consensus divergence, invalid state transitions, incorrect network-version gates
onetimesecretCopilot instructionsonetimesecret/onetimesecret/.github/copilot-instructions.md
that fails without them. - Typos in comments or docs, unless they invert the meaning. - Test file organization or helper placement. - Pre-existing code not changed in this
sonic-netCopilot instructionssonic-net/SONiC/.github/copilot-instructions.md
YANG, REST API 10. **Warm boot support**: How the feature handles warm restart 11. **Testing**: Test plan overview 12. **References**: Related documents and specifications ## Language & Style - **Documentation**: Markdown (`.md` files
No other project uses it yet
inspektor-gadgetCopilot instructionsinspektor-gadget/inspektor-gadget/.github/copilot-instructions.md
Kubernetes clusters and Linux hosts. Gadgets are eBPF programs packaged as OCI images. ## Build & Test Commands ```bash # Build ig (standalone Linux tracer) make ig # Build kubectl-gadget (Kubernetes plugin) make
Steady3 mentions in 2 weeks
No other project uses it yet
OpenMindCopilot instructionsOpenMind/OM1/.github/copilot-instructions.md
Copilot Instructions ## Tooling / Dependencies - We use **Make** for building, testing, and running the project. - Dependencies are managed via Go modules (`go.mod` and `go.sum`). - Use these make commands: - Build: `make build
streetpeaCopilot instructionsstreetpea/chiaki-ng/.github/copilot-instructions.md
build -G Ninja -DCMAKE_BUILD_TYPE=Release` - `cmake --build build --target chiaki` - Unit tests live in `test/` and build into `chiaki-unit`: - `cmake -S . -B build -DCHIAKI_ENABLE_TESTS
No other project uses it yet
srl-labsCopilot instructionssrl-labs/containerlab/.github/copilot-instructions.md
lint` command when golangci is locally installed or `make clint` when using docker container. - Testing is done with `make test` command. ## Repository Structure - The CLI tool source code is located
Steady5 mentions in 2 weeks
No other project uses it yet
dotnetCopilot instructionsdotnet/macios/.github/copilot-instructions.md
Apple API bindings (Foundation, UIKit, AppKit, etc.) - `tools/` - Development tools (mtouch, mmp, linker, bgen) - `tests/` - Test suites (unit, introspection, extrospection) - `msbuild/` - MSBuild tasks and targets - `docs/` - Documentation and guides - `runtime
gem5Copilot instructionsgem5/gem5/.github/copilot-instructions.md
under `build/`. - Avoid changing `gem5/ext/` for dependency or policy work unless explicitly directed. - For tests, distinguish C++ GTests, Python PyUnit tests, and TestLib quick/long/very-long suites. - For CI/debugging, inspect concrete
No other project uses it yet
flightphpCopilot instructionsflightphp/core/.github/copilot-instructions.md
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, avoiding unnecessary
GitHubCopilot instructionsgithub/copilot-cli-for-beginners/.github/copilot-instructions.md
without explanation. - **Examples**: All code blocks and `copilot` commands must be copy-paste ready. Test them mentally before including. - **Naming**: Use kebab-case for session names, file names, and identifiers
No other project uses it yet
arminkCopilot instructionsarmink/FlashDB/.github/copilot-instructions.md
port/fal` | vendored third-party Flash Abstraction Layer - **do not review, do not suggest changes** | | `tests/*_tc.c` | utest cases, executed by CI under QEMU | | `docs/` | docsify documentation, `docs/zh-cn` is the Chinese
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.
