How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
entireioCopilot instructionsentireio/cli/.github/copilot-instructions.md
task-specific reference map](../CLAUDE.md#read-when-relevant) to find detailed architecture and development documentation. ## Testing Guidelines Write tests that provide real value, not just coverage: - **Test behavior, not implementation
MicrosoftCopilot instructionsmicrosoft/FluidFramework/build-tools/.github/copilot-instructions.md
tools and libraries for building, testing, releasing, and managing Fluid Framework repositories. For release documentation, use [conventional commits](../README.md#documenting-build-tools-changes), not changesets. **Runtime**: Node.js >=22.22.2, pnpm
MicrosoftCopilot instructionsmicrosoft/FluidFramework/.github/copilot-instructions.md
vice versa. ## Coding Guidelines Follow the [Coding Guidelines](../docs/content/Guidelines/Coding-Guidelines.md) when writing / modifying code. ## Documentation Guidelines Follow the [Documentation Guidelines](../docs/content/Guidelines/Documentation-Guidelines.md) when writing or modifying code or documentation. Read and follow
Microsoft AzureCopilot instructionsAzure/azure-powershell/.github/copilot-instructions.md
updated for changes) ### Development Workflow Files - `/tools/BuildScripts/BuildModules.ps1` - Core module build automation - `/tools/GenerateHelp.ps1` - Help documentation generation - `/tools/StaticAnalysis/` - Code analysis and validation tools - `/tools/Test/` - Testing infrastructure and utilities ## Typical Development Tasks ### Adding
MicrosoftCopilot instructionsmicrosoft/msquic/.github/copilot-instructions.md
CLOG config (`clog.sidecar`, `msquic.clog_config`) | | `scripts/` | PowerShell build/test/CI scripts (cross-platform via pwsh) | | `docs/` | Documentation: `BUILD.md`, `TEST.md`, `API.md`, `Architecture.md`, etc. | | `submodules/` | Git submodules: `googletest`, `quictls`, `openssl`, `clog`, `xdp-for-windows
MicrosoftCopilot instructionsmicrosoft/perfview/.github/copilot-instructions.md
region — this makes it easy to see all object state at a glance. ### Comments & Documentation - This codebase is **heavily commented** — maintain that standard. - Public types and public members exposed outside
MicrosoftCopilot instructionsmicrosoft/WindowsAppSDK/.github/copilot-instructions.md
Windows App SDK AI contributor guidance
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
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
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
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
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
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 `CLAUDE.md
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
MicrosoftCopilot instructionsmicrosoft/mcp/.github/copilot-instructions.md
Guidelines - Ensure all tests pass - Follow the [contribution guidelines](https://github.com/microsoft/mcp/blob/main/CONTRIBUTING.md) - Include appropriate documentation - Include tests that cover your changes - Update CHANGELOG.md with your changes - Run `.\eng\common\spelling
geekjourneyxCopilot instructionsgeekjourneyx/md2wechat-skill/.github/copilot-instructions.md
bash scripts/quality-gates.sh` runs this as step 0 (fail-fast, < 1 second) before lint/test. ### Documentation Sync Any change to CLI commands, flags, JSON output shape, providers, themes, or prompts must also
MicrosoftCopilot instructionsmicrosoft/WinUI-Gallery/.github/copilot-instructions.md
picked up by `AxeScanAllTests` which navigates to every page and asserts zero accessibility violations. ## Documentation Reference When looking up API references, control usage, or platform guidance, use the Microsoft Learn
MicrosoftCopilot instructionsmicrosoft/azure-pipelines-tasks/.github/copilot-instructions.md
Clean build directories package # Package tasks for distribution bump # Bump task versions gendocs # Generate documentation ``` ## Task Structure ### Key Files - `task.json` - Task definition and metadata - `task.loc.json` - Localization template (auto-generated) - `package.json
Ar9avCopilot instructionsAr9av/obsidian-wiki/.github/copilot-instructions.md
operation. ## Skills Reference | Skill | Folder | Purpose | |---|---|---| | Setup | `.skills/wiki-setup/` | Initialize vault structure | | Ingest | `.skills/wiki-ingest/` | Distill documents into wiki pages, plus any text data — chat exports, logs, transcripts | | History Router | `.skills/wiki-history-ingest/` | Route
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.
