How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
TanStackCopilot instructionsTanStack/ai/.github/instructions/copilot-instructions.md
there's a strong reason to introduce breaking changes. If breaking changes are necessary, document them clearly in the relevant documentation files. Under no circumstances should casting
MicrosoftCopilot instructionsmicrosoft/Generative-AI-for-beginners-dotnet/.github/copilot-instructions.md
organized in numbered folders (`01-IntroductionToGenerativeAI/` through `05-ResponsibleAI/`), each with a `readme.md` for documentation. - All code samples live in the centralized `samples/` directory, organized by category: `CoreSamples/`, `MAF/`, `AppsWithGenAI
MicrosoftCopilot instructionsmicrosoft/skills/.github/copilot-instructions.md
Rust** | `-rust` | `azure-identity-rust`, `azure-cosmos-rust` | ### Featured Skills | Skill | Purpose | |-------|---------| | `azure-search-documents-py` | Search SDK patterns, vector/hybrid search, agentic retrieval | | `azure-ai-agents-py` | Low-level agents
MicrosoftCopilot instructionsmicrosoft/DirectXTK/.github/copilot-instructions.md
ASCII characters in source files. HLSL files have separate indent/spacing rules defined in `.editorconfig`. - **Documentation**: The project provides documentation in the form of wiki pages available at [Documentation](https://github.com
MicrosoftCopilot instructionsmicrosoft/litebox/.github/copilot-instructions.md
affects public interfaces. - Extremely simple changes do not require explicit unit tests. 5. Document all public APIs and non-trivial implementation details. 6. Avoid introducing new dependencies unless strictly necessary
Microsoft AzureCopilot instructionsAzure/azure-sdk-for-java/.github/copilot-instructions.md
verify that your changes are correct, including any relevant tests or documentation checks. - Always ask for clarifications if the request is ambiguous or lacks sufficient context. - Always provide detailed justifications
MicrosoftCopilot instructionsmicrosoft/Olive/.github/copilot-instructions.md
package directory with core functionality - `test/` -- Test suite with requirements-test*.txt files - `docs/` -- Documentation - `.github/workflows/` -- CI/CD pipelines (lint.yml, codeql.yml) - `olive/passes/onnx` -- Directory of ONNX transformations passes - `olive/passes/pytorch` -- Directory of Pytorch
MicrosoftCopilot instructionsmicrosoft/pxt/.github/copilot-instructions.md
semantic versioning for all packages - Maintain backward compatibility when possible - Write clear, self-documenting code with JSDoc comments - Follow the existing code style and patterns in each component ## Architecture Principles
Microsoft AzureCopilot instructionsAzure/azure-sdk-for-js/.github/copilot-instructions.md
canonical home (skills under `.github/skills/`, reviewer instructions under `.github/instructions/reviewer/`, and deep-dive docs under `documentation/`) so the same rule isn't duplicated across files. Start there. This file is intentionally
muxy-appCopilot instructionsmuxy-app/muxy/.github/copilot-instructions.md
tests to understand established patterns. - Apply security, maintainability, architecture, resource usage, concurrency, testing, documentation, and extension requirements only where they are relevant to the changed behavior. - Identify root-cause problems
MicrosoftCopilot instructionsmicrosoft/DirectXTex/.github/copilot-instructions.md
ASCII characters in source files. HLSL files have separate indent/spacing rules defined in `.editorconfig`. - **Documentation**: The project provides documentation in the form of wiki pages available at [Documentation](https://github.com
Microsoft AzureCopilot instructionsAzure/AKS/.github/copilot-instructions.md
targeted patterns. --- ## Part 1: Repository Standards ### Repository Overview This repository contains resources, examples, and documentation for the Azure Kubernetes Service (AKS) Engineering team: - **Production Website**: <https://blog.aks.azure.com> (Docusaurus blog
LumiwealthCopilot instructionsLumiwealth/lumibot/.github/copilot-instructions.md
tests for any new functionality you add. Additionally, ensure that all tests are well-documented and follow best practices
MicrosoftCopilot instructionsmicrosoft/maker.js/.github/copilot-instructions.md
with `git status` or `git diff --cached` 2. Ensure only source code, tests, and documentation are included 3. Check that no build artifacts or lockfiles are being staged for commit
Microsoft AzureCopilot instructionsAzure/azure-functions-host/.github/copilot-instructions.md
that XML doc comments are created for any public APIs. When applicable, include ` ` and ` ` documentation in the comments. ### Nullable Reference Types * Declare variables non-nullable, and check for `null
MicrosoftCopilot instructionsmicrosoft/msticpy/.github/copilot-instructions.md
pytest markers: `unit`, `integration`, `slow` - **Tools**: `tools/` supplementary tools not core to the package - **Documentation**: `docs/` - Sphinx source files and notebooks ### Key Subpackages - `msticpy/data/` - Data providers and query execution - `msticpy/context
MicrosoftCopilot instructionsmicrosoft/snmalloc/.github/copilot-instructions.md
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 for structural
MicrosoftCopilot instructionsmicrosoft/openvmm/.github/copilot-instructions.md
written in Rust. This repository is home to both OpenVMM and OpenHCL (a paravisor). Documentation lives in `Guide/` and is published at https://openvmm.dev. ## Build & Setup Restore required dependencies before
MicrosoftCopilot instructionsmicrosoft/azure-pipelines-agent/.github/copilot-instructions.md
src/dev.cmd` (Windows) - **Agent Layout**: Built agent is placed in `{root}/{runtime_id}/_layout` - **Documentation**: Available in `docs/` directory ## Development Workflow ### Initial Setup ```bash # Clone and navigate to source git clone
Microsoft AzureCopilot instructionsAzure/azure-sdk-for-go/.github/copilot-instructions.md
answer is longer than a couple of sentences, provide a link to the reference document and a short summary of the answer. - For comprehensive agent guidance, see [AGENTS.md](https://github.com
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.
