How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
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
ElasticCopilot instructionselastic/apm-agent-java/.github/copilot-instructions.md
repository contains the Elastic APM Java agent. These instructions apply when reviewing pull requests. ## Review priorities - Prioritize correctness, compatibility, and operational safety over style. - Focus findings on problems introduced
agentic-inCopilot instructionsagentic-in/elephant-agent/.github/copilot-instructions.md
GitHub Copilot Instructions This repository uses an agent harness. Treat code suggestions and review comments as changes to that harness, not as isolated edits. ## Source Of Truth Order Follow
raids-labCopilot instructionsraids-lab/crater/.github/copilot-instructions.md
Crater 项目通用准则 此文档定义了项目开发的通用标准，并规定了所有指令文档的执行等级，适用于 GitHub Copilot 的所有智能体（`coding-agent` 与 `code-review`）。 --- ## 执行等级定义 (Guideline Levels) 项目中所有的子指令文档（`*.instructions.md`）及本文档中的准则均遵循以下两个等级，智能体必须根据自身角色执行对应动作： - **核心规范 (Core Requirements / MUST)**: - **`coding-agent`**: 应以最终产出物符合规范为目标。在处理具体任务时，应优先精准执行当前指令，并通过
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
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
osocietyCopilot instructionsosociety/vernet/.github/copilot-instructions.md
/GRAPH_REPORT.md` only for broad architecture review or when query/path/explain do not surface enough context. Only read source files when (a) modifying/debugging specific code, (b) the graph lacks the needed detail
OpenDevicePartnershipCopilot instructionsOpenDevicePartnership/patina/.github/copilot-instructions.md
rustfmt` via `rustfmt.toml`. Always run `cargo make fmt` after editing code. ## Common Anti-Patterns Flag these patterns during review: 1. Using `mod.rs` instead of named module files 2. Raw slice/pointer
Microsoft AzureCopilot instructionsAzure/karpenter-provider-azure/.github/copilot-instructions.md
repository-root file `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` is the source
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
celestiaorgCopilot instructionscelestiaorg/celestia-core/.github/copilot-instructions.md
higher level when unsure. Don't repeat the review tag in the PR description; the title already carries it. ## Code Organization - Analyze the project structure entirely before deciding where something
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
esbmcCopilot instructionsesbmc/esbmc/.github/copilot-instructions.md
correct and portable ## Review Priorities 1. **Critical**: Soundness issues, memory safety bugs, undefined behavior 2. **High**: Logic errors, performance regressions, missing tests 3. **Medium**: Code quality, documentation gaps, minor inefficiencies
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
ClickHouseCopilot instructionsClickHouse/clickhouse-connect/.github/copilot-instructions.md
When performing a code review, use the `code-review` skill in `.github/skills/code-review/SKILL.md
goravelCopilot instructionsgoravel/framework/.github/copilot-instructions.md
GitHub Copilot Instructions This file provides rules for GitHub Copilot when reviewing pull requests in `goravel/framework`. ## Go Code Style - Use `any` instead of `interface{}`. - Do not shadow the built
open-telemetryCopilot instructionsopen-telemetry/semantic-conventions-genai/.github/copilot-instructions.md
conventions These instructions guide both human contributors and AI assistants (including GitHub's Copilot code reviewer) working in this repository. Path-specific guidance lives under `.github/instructions/` and applies automatically based
MicrosoftDocsCopilot instructionsMicrosoftDocs/power-platform/.github/copilot-instructions.md
produced the initial draft with minimal human authorship. - `ai-usage: ai-assisted` – Human-directed, reviewed, and edited with AI support. - Omit only for purely human-authored legacy content. If missing
zaxbysauceCopilot instructionszaxbysauce/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
operatonCopilot instructionsoperaton/operaton/.github/copilot-instructions.md
docs/decisions/` - Review existing ADRs before significant changes - Follow MADR format for new architectural decisions - Create ADRs for changes affecting multiple components or core functionality ### Common Development Workflows #### Making Code Changes
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.
