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.
hyperlight-devCopilot instructionshyperlight-dev/hyperlight/.github/copilot-instructions.md
code has tests and rustdoc following existing patterns. 5. Docs updated if behavior documented in `README.md` or `docs/` changed. ## Code conventions * Follow idiomatic Rust and match the surrounding code style
Steady10 mentions in 2 weeks
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/PyRIT/.github/copilot-instructions.md
Style nitpicks that ruff/isort would catch automatically - Missing docstrings or comments — we prefer minimal documentation. Code should be self-explanatory. - Suggestions to add inline comments, logging, or error handling that
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/WindowsAppSDK/.github/copilot-instructions.md
Windows App SDK AI contributor guidance
NewFutureCopilot instructionsNewFuture/DDNS/.github/copilot-instructions.md
feedback until merge-ready. ## Cloud environment `.github/workflows/copilot-setup-steps.yml` prepares Python, pinned Ruff, Node.js, and locked documentation dependencies. Use the prepared toolchain and run DDNS directly from the repository root; source-based
magefileCopilot instructionsmagefile/mage/.github/copilot-instructions.md
that embed `mg.Namespace`. The type name becomes a CLI prefix (e.g., `mage ns:target`). - **Documentation** — All functions, methods, types, package variables, and package constants must have Go doc comments describing
No other project uses it yet
aquasecurityCopilot instructionsaquasecurity/tracee/.github/copilot-instructions.md
validation ## Continuous Integration & Validation ### PR Workflow (`.github/workflows/pr.yaml`) The PR workflow runs these checks: 1. **Documentation verification** - Man page sync validation 2. **Code verification** - Formatting, linting, vet, staticcheck, errcheck, govulncheck
MetaCubeXCopilot instructionsMetaCubeX/metacubexd/.github/copilot-instructions.md
packages/agent/MANUAL.md](../packages/agent/MANUAL.md) contains real-kernel smoke tests that are intentionally outside CI. - [README.md](../README.md) documents supported deployment forms. ## Monorepo Map This is a pnpm 10 workspace with four workspaces: | Workspace
prestCopilot instructionsprest/prest/.github/copilot-instructions.md
rows.Close`, response bodies, etc.). - Preserve thread-safety assumptions in cache, middleware, and shared components. ## Documentation and Developer Experience - Update docs/comments only when behavior changes or new setup is required. - Keep
Steady2 mentions in 2 weeks
No other project uses it yet
Model Context ProtocolCopilot instructionsmodelcontextprotocol/csharp-sdk/.github/copilot-instructions.md
warnings as errors ### Code Style - Follow the conventions in `.editorconfig` - Use clear, descriptive XML documentation comments for public APIs - Follow async/await patterns consistently - Use file-scoped namespaces: `namespace ModelContextProtocol.Client;` ### Naming
Steady3 mentions in 2 weeks
No other project uses it yet
IvanMurzakCopilot instructionsIvanMurzak/Unity-MCP/.github/copilot-instructions.md
Conventions - **MCP Tools**: Implemented using attributes in the Plugin. Reflection-based access via `ReflectorNet`. - **Documentation**: - [Unity-MCP.wiki](Unity-MCP.wiki/) for user docs. - [docs/](docs/) for translations and repo docs. - See `AGENTS.md
crmneCopilot instructionscrmne/ruby_llm/.github/copilot-instructions.md
layers with no wire vocabulary in the domain; and the work is small, tested, documented, and free of implementation comments. ## Framework structure RubyLLM is an AI framework with two main
No other project uses it yet
EvolvingLMMs-LabCopilot instructionsEvolvingLMMs-Lab/lmms-eval/.github/copilot-instructions.md
fields in the PR template for exact commands, model/data/hardware, results, and evidence. If blocked, document the attempt and keep the PR in draft; never invent successful validation
No other project uses it yet
dvorkaCopilot instructionsdvorka/hstr/.github/copilot-instructions.md
Copilot instructions This document provides instructions to the copilot AI assistants and agents. ## General instructions - Write beautiful code. - Handle for errors, and exceptions and corner cases. - Do good
CysharpCopilot instructionsCysharp/MagicOnion/.github/copilot-instructions.md
presence of unit tests. Suggest fixes for any sections that deviate from these points. ## Documentation Review Guidelines When reviewing changes to documentation, focus on the following points: - Spelling - Clarity
alextselegidisCopilot instructionsalextselegidis/easyappointments/.github/copilot-instructions.md
relevant to the task. * Do not refactor unrelated parts of the codebase unless necessary. ## Documentation * Update relevant documentation when behavior changes. * Keep README and usage instructions accurate. ## Final Check Before
MicrosoftCopilot instructionsmicrosoft/FLAML/.github/copilot-instructions.md
avoid formatting issues ### Pull Requests - Ensure all tests pass before requesting review - Update documentation if adding new features - Follow the PR template in `.github/PULL_REQUEST_TEMPLATE.md` - ALWAYS run `pre-commit
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/ApplicationInspector/.github/copilot-instructions.md
names for variables, methods, and classes - Keep methods focused and single-purpose - Add XML documentation comments for public APIs - Use nullable reference types where appropriate - Prefer `var` for local variables
hzellerCopilot instructionshzeller/rpi-rgb-led-matrix/.github/copilot-instructions.md
library with an explicit C-callable interface and call it from C. Document its build integration, dependencies, memory ownership, and error behavior. Do not introduce Go when no web behavior
No other project uses it yet
MongoDBCopilot instructionsmongodb/mongo-python-driver/.github/copilot-instructions.md
ensure proper separation of concerns. - All public classes, modules, and methods should have clear documentation in Sphinx format. ## PyMongo-specific Concerns - Do not review files within `pymongo/synchronous` or files
Steady4 mentions in 2 weeks
No other project uses it yet
dotnetDeletes or force-pushesCopilot instructionsdotnet/fsharp/.github/copilot-instructions.md
symbol` — the symbol graph, not `grep` plus hand edits. - Format what you touched with `document_format` / `document_organize_imports` before reaching for `dotnet fantomas`. Before editing a file on disk
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.
