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.
V-IOLE-TCopilot instructionsV-IOLE-T/tab-harbor/.github/copilot-instructions.md
When performing a code review, respond in Simplified Chinese. ## Design Context ### Product Overview Tab Harbor is a calmer Chrome new tab workspace for people who live with many open tabs
github-copilot-resourcesReads credentialsCopilot instructionsgithub-copilot-resources/copilot-metrics-viewer/.github/copilot-instructions.md
Nuxt 3 web application for GitHub Copilot usage metrics and analytics
vrc-getCopilot instructionsvrc-get/vrc-get/.github/copilot-instructions.md
writing code: - Please don't make localization for locales other than en / ja. I cannot review those locales. - Run cargo clippy for lints and cargo fmt for format before commit
ZcashFoundationCopilot instructionsZcashFoundation/zebra/.github/copilot-instructions.md
description is incomplete, ask questions before making strong claims. ## Contribution Process Checks Before reviewing code quality, verify: - [ ] PR links to a pre-discussed issue that a Zebra team member acknowledged
amdCopilot instructionsamd/xdna-driver/.github/copilot-instructions.md
Review context for xdna-driver ## Layout - drivers/accel/amdxdna/: DRM accel kernel driver (amdxdna.ko), Linux upstream style. - aie2_*: AIE2 backend (NPU1, NPU4, NPU5, NPU6). - aie4_*: AIE4 backend (NPU3), PCI classic
josixCopilot instructionsjosix/awesome-claude-md/.github/copilot-instructions.md
Feature Name]** - **[Aspect]**: [Description] - **[Commands/Examples]**: [Specific examples] ## Specific Techniques to Learn ### [Technique Name] ```[language] [Code example] ``` [Explanation] ## Key Takeaways 1. **[Takeaway 1]**: [Description] 2. **[Takeaway 2]**: [Description] ``` ### README.md Updates When
QuantcoCopilot instructionsQuantco/dataframely/.github/copilot-instructions.md
arrange" step, the respective logic should be extracted into a fixture ## Reviewing When reviewing code changes, make sure that the `SKILL.md` is up-to-date and in line with
provosReads credentialsCopilot instructionsprovos/ironcurtain/.github/copilot-instructions.md
IronCurtain Copilot Review Instructions IronCurtain is a secure agent runtime that mediates between an AI agent and MCP servers. Every tool call passes through a trusted process that evaluates
MicrosoftCopilot instructionsmicrosoft/vcpkg-tool/.github/copilot-instructions.md
helper executables (`reads-stdin`, `test-editor`, etc.) used by tests. - The `vcpkg-artifacts` TypeScript code is bundled into `vcpkg-artifacts.mjs` during CMake builds only when `VCPKG_ARTIFACTS_DEVELOPMENT=ON` (enabled
openvinotoolkitCopilot instructionsopenvinotoolkit/openvino.genai/.github/copilot-instructions.md
that linters already check. ## General Coding Guidelines Follow these rules when writing, modifying, or reviewing code in this repository. Rules are grouped by topic. ### Correctness 1. Don't adjust config
SukramJCopilot instructionsSukramJ/homematicip_local/.github/copilot-instructions.md
Base entity class | | `const.py` | Constants & enums | | `strings.json` | UI strings (primary source) | | `manifest.json` | Integration metadata | ## Code Review Focus Areas When reviewing code or generating suggestions: 1. **Type Safety**: Ensure full type
FerroxLabsCopilot instructionsFerroxLabs/wayland/.github/copilot-instructions.md
improve adjacent code, comments, or formatting. No speculative features. No abstractions for single-use code. Simplest solution that works. Self-verify before destructive or irreversible actions. Plan before complex tasks
phpCopilot instructionsphp/doc-en/.github/copilot-instructions.md
Code Review Policy - When performing a code review, do not add any review comments. - When performing a code review, do not suggest any changes. - When performing a code review, respond
WoWAnalyzerCopilot instructionsWoWAnalyzer/WoWAnalyzer/.github/copilot-instructions.md
follow-up questions as per **[Follow-up Questions](instructions/follow-up-questions.instructions.md)** ## Routing When performing a code review, apply the checks in **[PR Review](instructions/copilot-pr-review.instructions.md)**. When validating changes locally, use **[Build & Testing](instructions/build.instructions.md
MicrosoftDocsCopilot instructionsMicrosoftDocs/powerapps-docs/.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
nodetool-aiReads credentialsCopilot 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
open-telemetryCopilot instructionsopen-telemetry/opentelemetry-ebpf-instrumentation/.github/copilot-instructions.md
Copilot Instructions - Read `AGENTS.md` and `CONTRIBUTING.md` before suggesting code, reviewing a PR, or answering repository-specific questions. Treat them as the source of truth. - Start with `devdocs/pipeline-map.md` when you need
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.
