How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
MicrosoftCopilot instructionsmicrosoft/DevSkim/.github/copilot-instructions.md
target the `main` branch 3. PRs require: - Changelog.md update - Passing CI/CD checks - Code review approval 4. Merges use **squash merge** strategy ## Additional Resources - [Build from Source](https://github.com/microsoft/DevSkim/wiki/Build-from-Source) - [Writing
NVIDIACopilot instructionsNVIDIA/cudf-spark/.github/copilot-instructions.md
memory allocation semantics, null handling) - **NVIDIA/cudf-spark-jni** — verify JNI binding signatures, memory ownership rules, error codes ## Review Checklist - [ ] C1: Resource leaks — AutoCloseable not closed on exception paths; use withResource/closeOnExcept/safeClose, never bare
MicrosoftCopilot instructionsmicrosoft/vstest/.github/copilot-instructions.md
only changes (e.g. `.md` files) — these PRs go green in under a minute. - For code changes, check PR status within 15–20 minutes — the Windows build and tests finish first
Microsoft AzureCopilot instructionsAzure/azure-service-operator/.github/instructions/copilot-instructions.md
clarification. ## Key Guidelines 1. Follow Go best practices and idiomatic patterns 2. Maintain existing code structure and organization 3. Write unit tests for new functionality. Use table-driven unit tests
MicrosoftCopilot instructionsmicrosoft/OpenAIWorkshop/.github/copilot-instructions.md
Results**: Add review section to `tasks/todo.md` 6. **Capture Lessons**: Update `tasks/lessons.md` after corrections ## Core Principles - **Simplicity First**: Make every change as simple as possible. Impact minimal code. - **No Laziness**: Find
MicrosoftCopilot instructionsmicrosoft/CCF/.github/copilot-instructions.md
comments. Run `scripts/ascii-checks.sh` for its covered files. Apply the character policy above when reviewing changed code and agent instructions outside its coverage; exclusions other than Lean do not permit
MicrosoftCopilot instructionsmicrosoft/binskim/.github/copilot-instructions.md
files directly. - Follow the platform-specific rule and test layout documented in `docs\RuleContributions.md`. - Review generated SARIF baselines when rule applicability, messages, or output changes. ## Parser and driver changes - Treat
MicrosoftCopilot instructionsmicrosoft/DirectXMesh/.github/copilot-instructions.md
FROM_WIN32(ERROR_INVALID_NAME)` | | `E_BOUNDS` | `0x8000000BL` (conditionally defined if not already present) | ## Code Review Instructions When reviewing code, focus on the following aspects: - Adherence to coding standards defined
MicrosoftCopilot instructionsmicrosoft/MIEngine/.github/copilot-instructions.md
code belongs | [Architecture-for-AI.md](../docs/Architecture-for-AI.md) (and the project wiki: [Architecture-of-the-MIEngine](https://github.com/microsoft/MIEngine/wiki/Architecture-of-the-MIEngine), [Architecture-of-OpenDebugAD7](https://github.com/microsoft/MIEngine/wiki/Architecture-of-OpenDebugAD7), [Architecture-of-DebugAdapterRunner](https://github.com/microsoft/MIEngine/wiki/Architecture-of-DebugAdapterRunner)) | | Writing or reviewing
sirkirbyCopilot instructionssirkirby/unifi-mcp/.github/copilot-instructions.md
context. - Treat changes to agent-governance files as lower-trust and require human code-owner review. - All findings and dispositions are advisory. A human maintainer retains final approval and merge
utensilsCopilot instructionsutensils/mcp-nixos/.github/copilot-instructions.md
tests # Run all tests with coverage lint # Check code with ruff format # Format code with ruff typecheck # Run mypy type checker build # Build package distributions ``` **Python-only alternative
Microsoft AzureCopilot instructionsAzure/azure-cosmos-dotnet-v3/.github/copilot-instructions.md
description. 3. **Preview-feature carve-out.** If the change is to a preview-only code path *and* it could affect default-config semantics for any customer in the next
MongoDBCopilot instructionsmongodb/docs/.github/copilot-instructions.md
example testing" - `platform\` - refer to "When working on platform" When you are performing a code review, apply the instructions based on the file paths of the files
MetaCopilot instructionsfacebookresearch/balance/.github/copilot-instructions.md
Code Review Instructions: `balance` (Python) Review instructions for the **balance** Python package (weighting and balancing utilities for correcting bias in tabular datasets). Prioritize correctness, statistical validity, reproducibility, and backward compatibility
Microsoft AzureCopilot instructionsAzure/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.
MicrosoftCopilot instructionsmicrosoft/teams-sdk/.github/copilot-instructions.md
command parsing, MSAL for auth, and talks to TDP (Teams Developer Portal) APIs. ## Review Style Be extremely concise — sacrifice grammar for brevity. Every comment MUST include an importance level prefix
MicrosoftCopilot instructionsmicrosoft/winget-create/.github/copilot-instructions.md
bodies; open a pull request or link a branch when code is available. - Before opening a pull request, review `CONTRIBUTING.md`, follow the PR template, keep the change focused, and summarize
MicrosoftCopilot instructionsmicrosoft/agent-framework-go/.github/copilot-instructions.md
consumer, not checked in. ## Pull request reviews Use the following guidance when reviewing a pull request. Check callers and documented contracts before reporting a defect. Explain the concrete failure
FerroxLabsCopilot instructionsFerroxLabs/wayland/.github/copilot-instructions.md
improve adjacent code, comments, or formatting. No speculative features. No abstractions for single-use code. Simplest solution that works. Self-verify before destructive or irreversible actions. Plan before complex tasks
MicrosoftCopilot instructionsmicrosoft/vcpkg-tool/.github/copilot-instructions.md
helper executables (`reads-stdin`, `test-editor`, etc.) used by tests. - The `vcpkg-artifacts` TypeScript code is bundled into `vcpkg-artifacts.mjs` during CMake builds only when `VCPKG_ARTIFACTS_DEVELOPMENT=ON` (enabled
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.
