How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
MicrosoftCopilot instructionsmicrosoft/kiota/.github/copilot-instructions.md
Prefer non-destructive actions and do not revert unrelated local changes. ## Security review defaults When modifying code generation or writer/refiner logic, treat schema-derived values as untrusted and ensure literal
MicrosoftCopilot instructionsmicrosoft/mcp/.github/copilot-instructions.md
/microsoft/mcp/blob/main/docs/recorded-tests.md) in `docs/recorded-tests.md` for more details on how to convert and validate recorded tests. ## Code Review Guidelines When reviewing a pull request, use the `mcp-code-reviewer` skill. In interactive
AvdLeeCopilot instructionsAvdLee/SwiftUI-Agent-Skill/.github/copilot-instructions.md
this repository are **reference patterns for AI agents**, not compilable sample code for human developers. When reviewing: - **Do not flag "incomplete" snippets.** Examples intentionally omit surrounding struct/class context, imports
TanStackCopilot instructionsTanStack/ai/.github/instructions/copilot-instructions.md
Provide project context and coding guidelines that AI should follow when generating code, answering questions, or reviewing changes. Whenever you want to build the packages to test if they work
oceanbaseCopilot instructionsoceanbase/seekdb/.github/copilot-instructions.md
When performing a pull request code review, read and follow `/.agents/skills/code-review/SKILL.md
MicrosoftCopilot instructionsmicrosoft/Generative-AI-for-beginners-dotnet/.squad/templates/copilot-instructions.md
starting work, check your capability profile in `.squad/team.md` under the **Coding Agent → Capabilities** section. - **🟢 Good fit** — proceed autonomously. - **🟡 Needs review** — proceed, but note in the PR description that a squad
MicrosoftCopilot instructionsmicrosoft/DirectXTK/.github/copilot-instructions.md
level feature checks | > `_M_ARM` / `__arm__` is legacy 32-bit ARM which is deprecated. ## Code Review Instructions When reviewing code, focus on the following aspects: - Adherence to coding standards defined
GitHubCopilot instructionsgithub/copilot-cli-for-beginners/.github/copilot-instructions.md
code blocks and `copilot` commands must be copy-paste ready. Test them mentally before including. - **Naming**: Use kebab-case for session names, file names, and identifiers (e.g., `book-app-review
Microsoft AzureCopilot instructionsAzure/azure-sdk-for-java/.github/copilot-instructions.md
NEVER turn off any Checkstyle or SpotBugs rules to resolve linting issues. - Always review your own code for consistency, maintainability, and testability - Always ask how to verify that your changes
KuddevCopilot instructionsKuddev/nebula/.github/copilot-instructions.md
Review guidance Review concrete regressions and missing boundary cases in the changed code. Explain an actionable finding with the trigger, affected behavior, and file/line evidence. Distinguish confirmed defects from questions
MicrosoftCopilot instructionsmicrosoft/CsWin32/.github/copilot-instructions.md
Copilot instructions for this repository ## High level guidance * Review the `CONTRIBUTING.md` file for instructions to build and test the software. * Set the `NBGV_GitEngine` environment variable to `Disabled` before running
muxy-appCopilot instructionsmuxy-app/muxy/.github/copilot-instructions.md
Code Review Review every pull request for specification compliance and applicable repository standards using one evidence-gathering pass. Do not build, lint, run tests, or modify code during a review
MicrosoftCopilot instructionsmicrosoft/DirectXTex/.github/copilot-instructions.md
ERROR_FILE_TOO_LARGE)` | | `HRESULT_E_CANNOT_MAKE` | `HRESULT_FROM_WIN32(ERROR_CANNOT_MAKE)` | ## Code Review Instructions When reviewing code, focus on the following aspects: - Adherence to coding standards defined
MicrosoftCopilot instructionsmicrosoft/maker.js/.github/copilot-instructions.md
repository. ## Before Committing Always: 1. Review the files being committed with `git status` or `git diff --cached` 2. Ensure only source code, tests, and documentation are included 3. Check that
Microsoft AzureCopilot instructionsAzure/azure-functions-host/.github/copilot-instructions.md
General * Make only high-confidence suggestions when reviewing code changes. * Always use the latest version of C#, currently C# 13 features. * Never change global.json unless explicitly asked to. * Never change
MicrosoftCopilot instructionsmicrosoft/snmalloc/.github/copilot-instructions.md
prompt: instead of reading changed files and running tests, the reviewer should read the plan document, read existing code the plan references, verify assumptions about the codebase, and check
MicrosoftCopilot instructionsmicrosoft/openvmm/.github/copilot-instructions.md
subtle and needs human review **Error handling across trust boundaries:** - Use `thiserror` for typed error enums at library/API boundaries and protocol-facing code - Use `anyhow` with `.context("...")` for application-level
Microsoft AzureCopilot instructionsAzure/azure-sdk-for-go/.github/copilot-instructions.md
entire module name. ## Generated Code — DO NOT suggest changes When performing a code review, if a file contains the header `// Code generated by Microsoft (R) Go Code Generator
MicrosoftCopilot instructionsmicrosoft/DirectXMath/.github/copilot-instructions.md
technically valid but inconsistent with the project's convention and suppresses `-Wundef` unnecessarily. ## Code Review Instructions When reviewing code, focus on the following aspects: - Adherence to coding standards defined
MicrosoftCopilot instructionsmicrosoft/DirectXTK12/.github/copilot-instructions.md
integration in GraphicsMemory | > `_M_ARM` / `__arm__` is legacy 32-bit ARM which is deprecated. ## Code Review Instructions When reviewing code, focus on the following aspects: - Adherence to coding standards defined
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.
