How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
MicrosoftCopilot instructionsmicrosoft/go-sqlcmd/.github/copilot-instructions.md
line as a hostile reviewer, not the author. For each addition, ask: (1) Is this used? grep for it. (2) Is this consistent with parallel code? Check sibling maps/lists
Microsoft AzureCopilot instructionsAzure/azure-dev/.github/copilot-instructions.md
Azure Developer CLI (azd) - Instructions for Copilot Chat and Copilot code review For any work in this repository, especially for code reviews, you MUST read [cli/azd/AGENTS.md](../cli/azd/AGENTS.md) in its entirety
JayPokaleCopilot instructionsJayPokale/Chisle/.github/copilot-instructions.md
dependency solves it? 6. Can it be one line? 7. Only then: the minimum code that works. No unrequested abstractions. Deletion over addition. Shortest diff wins, after you understand
MicrosoftCopilot instructionsmicrosoft/WindowsProtocolTestSuites/.github/copilot-instructions.md
validation ## References & Key Files - [README.md](../README.md) - Overview of all test suites - [CONTRIBUTING.md](../CONTRIBUTING.md) - CLA, code review requirements - [ProtoSDK/README.md](../ProtoSDK/README.md) - EventSource instrumentation details - [TestSuites/FileServer/src/build.ps1](../TestSuites/FileServer/src/build.ps1) - Build pattern reference - [NuGet.config](../NuGet.config) - Package
Microsoft AzureCopilot instructionsAzure/karpenter-provider-azure/.github/copilot-instructions.md
unschedulable workloads. Read [AGENTS.md](../AGENTS.md) for the architecture, provisioning modes, code layout, validation commands, and the full pull request review guidelines. This file is the short form; `AGENTS.md
irockelCopilot instructionsirockel/tda/.github/copilot-instructions.md
Avoid absolute positioning. - **Accessibility:** Ensure components have appropriate tooltips and mnemonic keys where applicable. ## Review Focus Areas - **Deadlock Detection:** Double-check the logic that identifies circular dependencies in monitor locks
MicrosoftCopilot instructionsmicrosoft/pxt-arcade/.github/copilot-instructions.md
Test examples with real scenarios - **Hardware Testing**: Validate on actual hardware devices when applicable ## Code Review Guidelines ### What to look for in PRs: 1. **Correctness**: Does the code solve
nodetool-aiCopilot instructionsnodetool-ai/nodetool/.github/copilot-instructions.md
safety across the codebase - Consistent code style and patterns - No regressions in existing functionality ## Code Review for Regressions After making changes and before submitting a PR, review your code
MicrosoftCopilot instructionsmicrosoft/AL-Go/.github/copilot-instructions.md
names with `-replace "[^a-z0-9\-]"`. ### Authentication - Never hardcode credentials or tokens in source code. - Use GitHub secrets or Azure KeyVault for credential storage. ## YAML Workflow Conventions - Declare minimal required
agentregistry-devCopilot instructionsagentregistry-dev/agentregistry/.github/copilot-instructions.md
Copilot Instructions Read and follow `AGENTS.md` for repo-local coding and workflow guidance. Before creating or updating a pull request, review the PR authoring rules in `AGENTS.md` and follow `.github/PULL_REQUEST_TEMPLATE.md
MicrosoftCopilot instructionsmicrosoft/PowerAppsCodeApps/samples/FluentSample/.github/copilot-instructions.md
logic should be reviewed. - Document or summarize your reasoning and decision-making if a change affects multiple components. --- # Using this template repository to build Power Apps Code App. Follow these
ZaxbyHubCopilot instructionsZaxbyHub/opencode-swarm/.github/copilot-instructions.md
ready. --- # Repository QA Standards These standards apply to all Copilot interactions including code generation and PR review. ## Security - Never hardcode secrets, tokens, API keys, or connection strings — use environment variables
MicrosoftCopilot instructionsmicrosoft/mssql-python/.github/copilot-instructions.md
ship code-only assessments. - Understand the linked issue and existing review threads before changing code. - Search existing issues and PRs before opening a new one — do not create duplicates
MicrosoftCopilot instructionsmicrosoft/Power-CAT-Copilot-Studio-Kit/.github/copilot-instructions.md
Copilot instructions — Power CAT Copilot Studio Kit These instructions guide the GitHub Copilot coding agent (and any human contributor reading them) when working in this repository. ## Repository at a glance
GitHubCopilot instructionsgithub/local-action/.github/copilot-instructions.md
relevant issues or discussions - Any additional context that may be helpful for reviewers ## Code Review Guidelines When performing a code review, please follow these guidelines: - If there are changes that
MicrosoftCopilot instructionsmicrosoft-foundry/foundry-samples/.github/copilot-instructions.md
cell in a notebook if it contains metadata with "name:" in it. In a code review, if any of the above rules are broken, please add the following text
Sidiora-LabsCopilot instructionsSidiora-Labs/LayerX-Network/.github/copilot-instructions.md
cycles, 30-minute cap, and the stop condition. They report exit code and log path only. No duplicate reviews, no extra verification campaigns. - **Agreed Result**: Once verify_cmd passes, publish
AvdLeeCopilot instructionsAvdLee/Swift-Testing-Agent-Skill/.github/copilot-instructions.md
GitHub Copilot Instructions: Agent Skills Expert (Swift Testing) Review changes as an **Agent Skills expert**, focusing on the **Agent Skills open format** specification and ensuring this repository stays a **Swift
MicrosoftCopilot instructionsmicrosoft/RAMPART/.github/copilot-instructions.md
PyRIT framework interaction (see coding standards for import rules). ## Instruction Files BEFORE editing or code-reviewing any file, you MUST read the `.github/instructions/` files whose `applyTo` patterns match the files
Community-AccessCopilot instructionsCommunity-Access/accessibility-agents/.github/copilot-instructions.md
Does | |--------|-------------| | audit-web-page | Full single-page audit with axe-core scan and code review | | quick-web-check | Fast axe-core triage - runtime scan only, pass/fail verdict | | audit-web-multi
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.
