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.
stacks-networkCopilot instructionsstacks-network/stacks-core/.github/copilot-instructions.md
Copilot PR review guidance for stacks-core ## Scope These instructions define pull-request review criteria, not code-generation requirements. Review the proposed diff and enough surrounding code to validate
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
Steady13 mentions in 2 weeks
No other project uses it yet
filecoin-projectCopilot instructionsfilecoin-project/lotus/.github/copilot-instructions.md
Copilot code review instructions Use `/AGENTS.md` for Lotus architecture, invariants and validation commands. Review the pull request's changed behaviour, not the repository in the abstract. Inspect relevant callers, interfaces
onetimesecretCopilot instructionsonetimesecret/onetimesecret/.github/copilot-instructions.md
Code review instructions ## Do not comment on - Locale `content_hash` values (missing, stale, or mismatched). CI gates these and `pnpm locales:hashes:apply` regenerates them. - Anything rubocop, eslint, or prettier
sonic-netCopilot instructionssonic-net/SONiC/.github/copilot-instructions.md
commits - **CLA**: Sign Linux Foundation EasyCLA - **HLD review**: Design documents require community review before merge - **Feature proposals**: Discuss in SONiC community meetings before submitting HLD - **Formatting**: Use consistent Markdown formatting
No other project uses it yet
inspektor-gadgetCopilot instructionsinspektor-gadget/inspektor-gadget/.github/copilot-instructions.md
gadget/macros.h>`, `<gadget/types.h>`, `<gadget/filter.h>`, `<gadget/buffer.h>`. - Use ` ` for kernel types (BTF-based, no kernel headers needed). - Code generation uses `bpf2go`: `//go:generate go run github.com/cilium/ebpf/cmd/bpf2go ...` - Prefer enums over strings in eBPF
No other project uses it yet
dotnetCopilot instructionsdotnet/macios/.github/copilot-instructions.md
user 'vs-mobiletools-engineering-service2' when processing issues and pull requests. ## Pull request review instructions - Don't report potential C# compilation errors (the compiler will report those). ## Repository Overview This
No other project uses it yet
GitHubCopilot instructionsgithub/copilot-cli-for-beginners/.github/copilot-instructions.md
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 (e.g., `book-app-review
Steady3 mentions in 2 weeks
No other project uses it yet
arminkCopilot instructionsarmink/FlashDB/.github/copilot-instructions.md
FlashDB code review instructions FlashDB is an ultra-lightweight embedded database for MCUs, written in plain C99 (no C++, no compiler extensions, no C11 atomics). It provides two databases
MicrosoftCopilot instructionsmicrosoft/DirectXTK/.github/copilot-instructions.md
level feature checks | > `_M_ARM` / `__arm__` is legacy 32-bit ARM which is deprecated. ## Code Review Instructions When reviewing code, focus on the following aspects: - Adherence to coding standards defined
tkemCopilot instructionstkem/cachetools/.github/copilot-instructions.md
constraints, boundaries and git workflow) live in [`AGENTS.md`](../AGENTS.md). This file adds only the code review process. ## Code Review - Reviews **amend `.github/copilot-review.md` in place** (header: date, commit, CI status, coverage
habitat-shCopilot instructionshabitat-sh/habitat/.github/copilot-instructions.md
tests and integration tests needed 4. **File Review**: Identify files that will be modified (avoiding prohibited files) ### 3. Implementation Phase 1. **Code Implementation**: - Follow Rust best practices and Habitat coding
intelCopilot instructionsintel/neural-compressor/.github/copilot-instructions.md
GitHub Copilot Instructions This file configures GitHub Copilot (code suggestions and PR reviews) to follow the coding standards enforced by the project's pre-commit hooks (`.pre-commit-config.yaml`) and tool configuration
nteractCopilot instructionsnteract/semiotic/.github/copilot-instructions.md
when a review claim depends on browser rendering, interaction, responsive layout, hydration, or accessibility. When an unstable custom lint fails, evaluate the rule as well as the code before recommending
CommunityToolkitCopilot instructionsCommunityToolkit/Maui/.github/copilot-instructions.md
Guidelines * Use GitHub Copilot to assist with code completion, documentation, and generating boilerplate code. * Always review and test the code suggested by GitHub Copilot to ensure it meets the project
flexpilot-aiCopilot instructionsflexpilot-ai/flexpilot-ide/.github/copilot-instructions.md
Coding Guidelines ## Introduction These are VS Code coding guidelines. Please also review our [Source Code Organisation](https://github.com/microsoft/vscode/wiki/Source-Code-Organization) page. ## Indentation We use tabs, not spaces. ## Naming Conventions * Use PascalCase
open-telemetryCopilot instructionsopen-telemetry/opentelemetry-java-instrumentation/.github/copilot-instructions.md
Instrumentation rules These rules and the applicable `.github/instructions/*.instructions.md` files guide both implementation and code review. Apply a rule only when its stated conditions hold. Keep its exceptions, rationale
bdringCopilot instructionsbdring/FluidNC/.github/copilot-instructions.md
channels; any can send commands, read responses - Enables multi-client control (web + serial simultaneously) ## Code Review Checklist - **Naming**: Follows CamelCase (classes), snake_case (methods, members with `_`) - **Includes**: Correct quotes (`"local
spiffeCopilot instructionsspiffe/spire/.github/copilot-instructions.md
processes, the SPIRE Server and the SPIRE Agent, plus a plugin system. When reviewing or generating code, weigh the concerns covered below. All of them matter, and more than
laude-instituteCopilot instructionslaude-institute/terminal-bench/.github/copilot-instructions.md
tests task completion. Be concise and to the point. Use the following criteria to review the task: 1. **Behavior in Task Description**: Check whether all behavior tested in the test
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.
