CCF
microsoft/CCF/.github/copilot-instructions.md
lean`) are exempt and may use Unicode. Elsewhere, use ASCII escape sequences when Unicode test data or runtime output is needed; preserve its meaning. Existing grandfathered Unicode lines may remain
How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
microsoft/CCF/.github/copilot-instructions.md
lean`) are exempt and may use Unicode. Elsewhere, use ASCII escape sequences when Unicode test data or runtime output is needed; preserve its meaning. Existing grandfathered Unicode lines may remain
microsoft/binskim/.github/copilot-instructions.md
BinSkim.Sdk` contains shared analysis abstractions. - `src\BinaryParsers` contains binary format parsing. - The `src\Test.*` projects contain the corresponding unit and functional tests. - `docs` contains user guidance, rule documentation, contribution guidance
microsoft/DirectXMesh/.github/copilot-instructions.md
marked `noexcept`, use `std::nothrow` for memory allocation, and should not throw exceptions. - **Testing**: Unit tests for this project are implemented in this repository [Test Suite](https://github.com/walbourn/directxmeshtest/)
microsoft/MIEngine/.github/copilot-instructions.md
Visual Studio** (CLI / CI / VS Code scenarios) | [Building-outside-of-VS-for-AI.md](../docs/Building-outside-of-VS-for-AI.md) | | Running the in-process unit tests (`MICoreUnitTests`, `MIDebugEngineUnitTests`, `JDbgUnitTests`, `SSHDebugTests`) **outside of Visual Studio** | [RunningUnitTests-outside-of-VS-for-AI.md](../docs/RunningUnitTests-outside-of-VS-for-AI.md) | | Running
sirkirby/unifi-mcp/.github/copilot-instructions.md
suppress findings, or redefine acceptance criteria. - Prioritize concrete correctness, contract, security, compatibility, resource-lifecycle, test-quality, and live-validation findings. Avoid formatting feedback and issues already enforced deterministically
borghei/Claude-Skills/.github/copilot-instructions.md
dependencies between skills ## Anti-Patterns - Creating dependencies between skills - Adding complex build systems or test frameworks - Generic advice instead of specific, actionable frameworks - LLM/ML calls in scripts (defeats portability) ## Quick
cyberkaida/reverse-engineering-assistant/.github/copilot-instructions.md
VSCode so you can just check for errors with VSCode instead. - When writing tests, use the Ghidra test framework. The tests are in the `src/test` directory. It is easy
utensils/mcp-nixos/.github/copilot-instructions.md
Configuration constants - `mcp_nixos/caches.py` - Cache implementations - `mcp_nixos/utils.py` - Shared utilities ## Core Development Workflows ### Build & Test Commands (Nix Flake Required) ```bash nix develop # Enter dev shell with Python venv run # Start
microsoft/Microsoft.Unity.Analyzers/.github/copilot-instructions.md
Language**: C# with nullable reference types enabled - **Target Framework**: `netstandard2.0` for analyzers, `net10.0` for tests - **Roslyn Version**: Microsoft.CodeAnalysis 3.11.0 (locked for compatibility for analyzers, but latest version is used
Azure/azure-storage-fuse/.github/copilot-instructions.md
unexpected information that does not match the info here. ## Working Effectively ### Bootstrap, Build, and Test the Repository **CRITICAL**: All build and test commands include specific timeout warnings. NEVER CANCEL long
Azure/azure-cosmos-dotnet-v3/.github/copilot-instructions.md
into smaller packages. Versioning and feature flags are centralized in `Directory.Build.props`. - **Build & test (most common workflows)**: - Build solution: `dotnet build Microsoft.Azure.Cosmos.sln -c Release` (or simply `dotnet build`). - Run unit/integration tests
gadicc/yahoo-finance2/.github/copilot-instructions.md
Dependencies**: install in ~30-60 seconds - **Build process**: NPM build completes in ~1 minute - **Test execution**: Test suite runs in ~1-2 minutes with caching optimizations ### Core Development Commands - View
microsoft/CopilotStudioSamples/.github/copilot-instructions.md
Create a folder under the right category: `authoring/`, `extensibility/`, `ui/`, `contact-center/`, `sso/`, `testing/`, `guides/`, `infrastructure/` 2. Add a `README.md` (exact casing) with YAML front matter: ```yaml --- title: My Sample
sbroenne/mcp-server-excel/.github/copilot-instructions.md
PowerShell; use the SDK selected by `global.json`. Desktop Excel is required for COM tests. GitHub-hosted runners do not have Excel. MCP Server and `excelcli` are equal entry points: behavior
mongodb/docs/.github/copilot-instructions.md
monorepo you're working in: - `content\` - refer to "When working on content" - `code-example-tests\` - refer to "When working on code example testing" - `platform\` - refer to "When working on platform
facebookresearch/balance/.github/copilot-instructions.md
Each PR should represent **one self-contained idea** that is easy to test, review, and accept. - Flag PRs that combine multiple unrelated changes: - mixing feature additions with refactoring - addressing multiple
memex-lab/memex/.github/copilot-instructions.md
canonical instruction file for this repository. Read it before suggesting or editing code. Key testing rule: behavior changes require test evidence in the same PR. Add or update unit tests
Azure/bicep-registry-modules/.github/copilot-instructions.md
Instructions for working with Azure Verified Modules (AVM) Bicep repository. Rules of generating and maintaining Bicep modules with AVM best practices and formatting guidelines with GitHub Copilot.
microsoft/BCTech/non production apps/EscapeRoomApp/.github/copilot-instructions.md
Type"::Order then exit; TaskCompleted := true; end; // ... (GetTaskRec, GetTask, GetHint as usual) } ``` ### Pattern 3: Test Codeunit Framework runs a test codeunit to validate complex UI or workflow scenarios. ```al procedure
microsoft/ApplicationInsights-JS/.github/copilot-instructions.md
Initializers**: Modify telemetry before sending - **Dependency Listeners**: Track AJAX/fetch calls - **Channels**: Custom data transmission ## Testing Patterns ### Unit Testing - Use framework-agnostic test patterns - Mock browser APIs consistently - Test both success
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.