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.
CheckmkCopilot instructionsCheckmk/checkmk/.github/copilot-instructions.md
those when suggesting changes. ## AI tooling lives elsewhere Reusable AI workflows for this project (code review, werk authoring, Gerrit/Jenkins/Jira/crash-report helpers, backports, etc.) are maintained as Claude Code plugins
No other project uses it yet
eventflowCopilot instructionseventflow/EventFlow/.github/copilot-instructions.md
install -r requirements.txt` followed by `mkdocs serve` when verifying doc updates. ## Coding conventions & review tips - Favor async APIs and accept `CancellationToken` parameters throughout—the core dispatchers expect cooperative cancellation
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
ntex-rsCopilot instructionsntex-rs/ntex/.github/copilot-instructions.md
Repository instructions These instructions are for working on ntex itself. Guidance for code that *uses* ntex is in `docs/llms.txt`, published at <https://docs.ntex.rs/llms.txt>. ## Layout Cargo workspace. `ntex
Steady6 mentions in 2 weeks
No other project uses it yet
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
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/Microsoft365DSC/.github/copilot-instructions.md
block, pass state through `PostProcessingArgs`. ## Code Formatting & Style These formatting rules are enforced during code review. Agents must apply them to all generated or modified PowerShell code: 1. **No trailing
omryCopilot instructionsomry/omegaconf/.github/copilot-instructions.md
Copilot instructions When generating code or reviewing pull requests for this repository, use `CONTRIBUTING.md` as the source of truth for contributor requirements. For pull request reviews, check the changed files
PSAppDeployToolkitCopilot instructionsPSAppDeployToolkit/PSAppDeployToolkit/.github/copilot-instructions.md
patterns over custom non-standard lifecycle hooks, especially for IDisposable/disposal implementations, to keep code review and commit ownership clear. - Avoid changes that cause `DialogManager` static initialization when the client/server process
OPCFoundationCopilot instructionsOPCFoundation/UA-.NETStandard/.github/copilot-instructions.md
analysis and fix all warnings - Follow the existing code structure and patterns - Check that your changes don't break compatibility - Review security implications of your changes - Contributors must agree
dotnetCopilot instructionsdotnet/iot/.github/copilot-instructions.md
existing pattern does so via an abstraction. - Don't capture `Console` I/O in library code (leave printing/logging to samples/apps). - Don't add hidden thread‑static caches or background threads without
MaintainerrCopilot instructionsMaintainerr/Maintainerr/.github/copilot-instructions.md
indexes all project docs: implementation guidance, conventions, architecture, and the release-review checklist. Before writing any code, read and follow the standing rules: [.github/instructions/implementation.instructions.md](instructions/implementation.instructions.md) and [.github/instructions/project-notes.instructions.md](instructions/project-notes.instructions.md). Other docs
Steady3 mentions in 2 weeks
No other project uses it yet
nelmioCopilot instructionsnelmio/NelmioApiDocBundle/.github/copilot-instructions.md
Contribution Guidelines: Enhanced Follow these mandatory guidelines when contributing code, documentation, and translations to this repository. All contributions will be reviewed for compliance. --- ## General Project Overview * **Project Scope:** This
Steady16 mentions in 2 weeks
No other project uses it yet
mampfesCopilot instructionsmampfes/hacs_waste_collection_schedule/.github/copilot-instructions.md
sources on `master`; for new pipeline sources use the release branch guide above. ## Things reviewers consistently reject - Hardcoded dates or weekday rules — sources must fetch from a real upstream
Steady2 mentions in 2 weeks
No other project uses it yet
zhaohongxuanCopilot instructionszhaohongxuan/obsidian-weread-plugin/.github/copilot-instructions.md
WeRead (微信读书) book metadata, highlights, notes, and reviews into Markdown files in an Obsidian vault. - The plugin supports login via WeChat QR code, cookie management, custom templates (Nunjucks), and flexible
Steady7 mentions in 2 weeks
No other project uses it yet
reubenoCopilot instructionsreubeno/brush/.github/copilot-instructions.md
implementation-and-provenance) required by `AGENTS.md`. Apply it to delegated agents and their tools. ## Code Review Checklist When reviewing PRs, verify: - [ ] **Documentation**: All exported APIs have rustdoc comments (missing docs
mfemCopilot instructionsmfem/mfem/.github/copilot-instructions.md
examples, tests, build or docs changes, and downstream APIs. 4. Analyze the code against the critical review pillars. 5. Compare the change against nearby code and MFEM patterns; flag unmotivated
timeplus-ioCopilot instructionstimeplus-io/proton/.github/copilot-instructions.md
claude/skills/build-and-verify/SKILL.md` for build, compile, run, and test tasks - Use `.claude/skills/cpp-coding/SKILL.md` for C++ code changes and reviews - Use `.claude/skills/sql-usage/SKILL.md` for streaming SQL work - Use `.claude/skills/review/SKILL.md` for PR or diff review
kubeflowCopilot instructionskubeflow/trainer/.github/copilot-instructions.md
GitHub Copilot Code Review Instructions ## Review Philosophy - Only comment when you have HIGH CONFIDENCE (>80%) that an issue exists - Be concise: one sentence per comment when possible - Focus on actionable
Steady4 mentions in 2 weeks
No other project uses it yet
home-assistantCopilot instructionshome-assistant/supervisor/.github/copilot-instructions.md
code, comments, and documentation. ## AI policy This project follows the [Open Home Foundation AI Policy](../AI_POLICY.md). Autonomous contributions are not accepted: a human must review, understand, and be able
alibabaCopilot instructionsalibaba/loongcollector/.github/copilot-instructions.md
part of the full suite 4. Coverage reporting is available through make targets ## Code Review Rule 你是一个高级代码审查助手，审查代码时要从QA角度仔细检查问题，以批判的眼光看待代码，以发现潜在问题为目的。 为了避免得到假阳性的检查结果，请注意： - 分析具体代码片段时要包含足够上下文，不要仅基于局部信息做出判断。 - 避免基于记忆进行代码分析，必须基于实际查看的代码。 - 在指出问题前，先理解业务逻辑的完整流程，考虑代码设计的合理性和必要性。 针对每个有变更的文件及其差异块
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.
