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.
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
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
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
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
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
Steady7 mentions in 2 weeks
No other project uses it yet
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
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
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
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
ExcelDataReaderCopilot instructionsExcelDataReader/ExcelDataReader/.github/copilot-instructions.md
dependencies and SDK-version-dependent package lock changes; see the explanation in `Directory.Build.props`. ## Public documentation - Add public reader APIs to the existing README API overview table and relevant usage section
Steady5 mentions in 2 weeks
No other project uses it yet
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
Steady5 mentions in 2 weeks
No other project uses it yet
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
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
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
redpanda-dataCopilot instructionsredpanda-data/console/.github/copilot-instructions.md
bisect` works. Parts of the history use Conventional Commits (`feat(frontend): ...`). `area:` is the documented standard in `CONTRIBUTING.md` and the form to use for new work. ## Pull requests - Title follows
No other project uses it yet
EasyCorpCopilot instructionsEasyCorp/EasyAdminBundle/.github/copilot-instructions.md
with single straight quotes - Use English in code, comments, commit messages and branch names ## Documentation - User documentation is stored in the doc/ directory - Use reStructuredText syntax for documentation - Use these
Steady5 mentions in 2 weeks
No other project uses it yet
kubeflowCopilot instructionskubeflow/pipelines/.github/copilot-instructions.md
listed in `.pre-commit-config.yaml` anyway. - Make sure that functions have clear docstrings and are well-documented. - Make sure that type hints are used consistently for Python code. - Make sure that logic
arcboxlabsCopilot instructionsarcboxlabs/arcbox/.github/copilot-instructions.md
images live under `tests/resources/` - Release boot assets (kernel + EROFS rootfs) are built in `arcboxlabs/boot-assets` ## Documentation References - Main [CLAUDE.md](../CLAUDE.md): project overview, architecture, commands - Crate-level READMEs in `app/`, `virt
xemu-projectCopilot instructionsxemu-project/xemu/.github/copilot-instructions.md
When performing a code review, consider developer documentation located at `/docs/devel`. Style guide is located at `/docs/devel/style.rst
Steady2 mentions in 2 weeks
2 projects use a version of this
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.
