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.
OneDragon-AnythingCopilot instructionsOneDragon-Anything/ZenlessZoneZero-OneDragon/.github/copilot-instructions.md
Handling**: 避免不必要的 try-catch。除非能进行有意义的处理，否则让异常抛出。 - **KISS Principle**: 保持代码简单。不要增加无用的代码、过度设计或非必要的抽象。 - **Testing/Docs**: 除非明确要求，否则不要主动创建测试脚本或文档。 # Code Review Guidelines (PR Review) 在进行代码审查或生成代码时，请严格遵守以下规则以减少无用的噪音： 1. **环境假设**：本项目主要针对 **1080p 分辨率** 和 **PC 平台**。 - **允许
No other project uses it yet
go-gitCopilot instructionsgo-git/go-git/.github/copilot-instructions.md
correctness, maintainability, test quality, and compatibility with upstream Git behavior. ## Review priorities - Prefer actionable review comments that explain the risk and suggest a concrete fix or follow-up. - Flag correctness
No other project uses it yet
kubernetes-sigsCopilot instructionskubernetes-sigs/headlamp/.github/copilot-instructions.md
when later commits fix or significantly rewrite code introduced by earlier commits in the same PR. - When this pattern appears, add a review finding asking the author to clean
No other project uses it yet
condaCopilot instructionsconda/conda/.github/copilot-instructions.md
GitHub Copilot Instructions for conda ## Code Review Policy **This repository does not use automated AI code review.** All code reviews in the conda project must be performed by human maintainers
No other project uses it yet
krausestCopilot instructionskrausest/js-framework-benchmark/.github/copilot-instructions.md
Those steps are described below in more detail * Pull PR * Review PR: Perform a code review and prompt me whether we should continue * Build PR: Pull the PR, build
No other project uses it yet
projectcalicoCopilot instructionsprojectcalico/calico/.github/copilot-instructions.md
description so a reviewer can ask for it. (The Copilot coding agent and automated review have no interactive user; a human-driven agent proposes the edit and waits for approval
No other project uses it yet
jokob-skCopilot instructionsjokob-sk/NetAlertX/.github/copilot-instructions.md
ROLE: NETALERTX ARCHITECT & STRICT CODE AUDITOR You are a cynical Security Engineer and Core Maintainer of NetAlertX. Your goal is to deliver verified, secure, and production-ready solutions. ### MANDATORY BEHAVIORAL
1 project uses a version of this
elementorCopilot instructionselementor/elementor/.github/copilot-instructions.md
rules completely - **Editing Existing Files**: Only apply rules to new code you add - **Code Reviews**: Check new code against these rules only --- ## Detailed Guidelines For comprehensive guidelines, see the following
No other project uses it yet
openmediavaultCopilot instructionsopenmediavault/openmediavault/.github/copilot-instructions.md
commands, please refer to the `AGENTS.md` file in the root of the repository. When reviewing code, use the conventions outlined below to ensure consistency and maintainability. Pay particular attention
No other project uses it yet
internetarchiveCopilot instructionsinternetarchive/openlibrary/.github/copilot-instructions.md
conventions; [`docs/ai-coding-guide.md`](../docs/ai-coding-guide.md) for architecture and data-model. Path-specific review guidance lives in [`instructions/`](instructions/). ### Code Style - **Python:** Ruff for linting and `ruff format` for formatting, line length
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/vscode-docs/.github/copilot-instructions.md
Code Docs Writing Guidelines Follow the [documentation writing guidelines](instructions/docs-writing.instructions.md) when reviewing or writing documentation
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/agent-governance-toolkit/.github/copilot-instructions.md
erodes trust. ## PR Review — Mandatory Before Merge NEVER merge a PR without thorough code review. CI passing is NOT sufficient. ### Review Output Style All PR reviews (human and bot) MUST
No other project uses it yet
Provenance-EmuCopilot instructionsProvenance-Emu/Provenance/.github/copilot-instructions.md
credentials - **project.pbxproj** — avoid when possible; prefer SPM Package.swift changes ### What NOT to Flag in Code Review - `force_cast` and `force_try` are intentionally warnings, not errors - Generated files (`Version.h`, `Version.swift
No other project uses it yet
open-edge-platformCopilot instructionsopen-edge-platform/anomalib/.github/copilot-instructions.md
Review added or modified entries, not unrelated historical formatting. Keep neighboring bullets contiguous without an extra blank line. - Flag missing fields with a concrete corrected entry even when code
Steady2 mentions in 2 weeks
No other project uses it yet
Microsoft AzureCopilot instructionsAzure/Azure-Sentinel/Tools/Microsoft-Sentinel-Classic-CLv1-Tables-Impact-Assessment/.github/copilot-instructions.md
refresh mapping from upstream CSVs .github/copilot-instructions.md # This file — global Copilot context .github/instructions/powershell.instructions.md # PowerShell-specific coding conventions .github/agents/sentinel-migration-assistant.md # Copilot custom agent for guided execution .github/workflows/update-solution-mapping.yml # Weekly GitHub Action to refresh mapping
No other project uses it yet
graphql-javaCopilot instructionsgraphql-java/graphql-java/.github/copilot-instructions.md
instead. You can disable wildcard imports in your IDE - Follow the code style defined in `graphql-java-code-style.xml`. ## Pull Request Review Guidelines ### Testing - If you add new functionality, or correct
No other project uses it yet
apacheCopilot instructionsapache/pinot/.github/copilot-instructions.md
terminology across documentation and code comments. - Document performance characteristics and limitations for important components. ## Code Review Process - Address all review comments thoughtfully; if you disagree, explain your reasoning clearly. - Keep
No other project uses it yet
Microsoft AzureCopilot instructionsAzure/azure-sdk-for-net/.github/copilot-instructions.md
needed. They may produce additional file changes that must be included in the commit. ## Code Review Before inspecting or commenting on any pull request, diff, patch, commit, or local changes
No other project uses it yet
agentgatewayCopilot instructionsagentgateway/agentgateway/.github/copilot-instructions.md
Copilot code review instructions Do not check for, speculate about, or report compilation errors during code review. Compilation diagnostics from review are frequently incorrect; rely on CI to detect
Steady12 mentions in 2 weeks
No other project uses it yet
inngestCopilot instructionsinngest/inngest/.github/copilot-instructions.md
regenerate after schema changes ### Protocol Buffers - Definitions in `proto/` directory - Uses `buf` for code generation - Run `make protobuf` to regenerate ## Common Tasks ### Adding New API Endpoints See `/docs/IMPLEMENTING_NEW_REST_API_V2_ENDPOINTS.md` for REST
No other project uses it yet
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.
