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.
GitHubCopilot instructionsgithub/codeql-action/.github/copilot-instructions.md
directory. A GitHub Actions workflow checks that the JavaScript code in `lib` is up-to-date. Therefore, you should not review any changes to the contents of the `lib` folder
Steady4 mentions in 2 weeks
No other project uses it yet
AvdLeeCopilot instructionsAvdLee/Swift-Concurrency-Agent-Skill/.github/copilot-instructions.md
GitHub Copilot Instructions: Agent Skills Expert Review code changes as an **Agent Skills expert**, focusing on the [Agent Skills open format](https://agentskills.io/home) specification and best practices. ## Core Agent
feiskyerCopilot instructionsfeiskyer/claude-code-settings/.github/copilot-instructions.md
Copilot when working with code in this repository. ## Environment Setup This repository contains Claude Code settings, configurations and guidance. The default setup uses GitHub Copilot as the model provider through
Steady2 mentions in 2 weeks
No other project uses it yet
pixeltableCopilot instructionspixeltable/pixeltable/.github/copilot-instructions.md
Copilot reviews Use root `AGENTS.md` for shared invariants and code review criteria. Matching `.github/instructions/*.instructions.md` files add scoped checks. Report verified, introduced defects with their trigger and user impact. Consolidate
Steady9 mentions in 2 weeks
No other project uses it yet
GZTimeWalkerCopilot instructionsGZTimeWalker/GZCTF/.github/copilot-instructions.md
Coding Agent Guide GZ::CTF is a full‑stack, production‑ready CTF platform for competitions and practice, designed for extensibility (dynamic/static challenges, containers, dynamic flags), observability (health/metrics/traces), and operability (rate
UbiquitousLearningCopilot instructionsUbiquitousLearning/mllm/.github/copilot-instructions.md
text that adheres to Rule 1. Rule 11 - Production Readiness: When reviewing or suggesting code, prioritize production-ready quality. This includes but is not limited to: a. Performance: - Evaluate time
MongoDBCopilot instructionsmongodb/mongo-php-library/.github/copilot-instructions.md
GitHub Copilot Instructions ## Code Review Guidelines ### Review Focus - **Do not repeat or paraphrase the PR description** - Only highlight changes or notable information that was omitted from the description - Focus
No other project uses it yet
pure-fishCopilot instructionspure-fish/pure/.github/instructions/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
amdCopilot instructionsamd/gaia/.github/copilot-instructions.md
canonical guidance: - `CLAUDE.md` — project conventions, coding rules, validation bar, docs policy - `AGENTS.md` — multi-agent coordination and PR workflow rules - `REVIEW.md` — PR review severity, nit budget, and review tone When guidance
Steady6 mentions in 2 weeks
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/hve-core/.github/copilot-instructions.md
Comprehensive coding guidelines and instructions for hve-core
wiresockCopilot instructionswiresock/proxifyre/.github/copilot-instructions.md
documentation - Analyze dependencies and configuration files - Review GitHub workflows and CI/CD processes - Make code changes for review (cannot test them) ## CI/CD Information ### GitHub Workflow Timing - **Build Process**: ~5-8 minutes
ccbrownCopilot instructionsccbrown/iocraft/.github/copilot-instructions.md
Referencing the pull request, the review, an issue discussion, or instructions given to an AI agent. - Restating what the next line of code obviously does. Comments should explain non-obvious
cgeoCopilot instructionscgeo/cgeo/.github/copilot-instructions.md
Prefer smaller, logically grouped commits; they will be squashed at the end - After every code change, automatically run all three quality gates (compile, unit tests, checkstyle) and fix any failures
No other project uses it yet
intelCopilot instructionsintel/llvm/.github/copilot-instructions.md
When performing a code review, pay close attention to code modifying a function's control flow. Could the change result in the corruption of performance profile data? Could the change
Surging1 mention in 2 weeks
1 project uses a version of this
SPlayer-DevCopilot instructionsSPlayer-Dev/SPlayer-Next/.github/copilot-instructions.md
SPlayer-Next Copilot 指引 本仓库所有 Copilot 会话、Code Review、建议，**一律使用中文作答**（代码、标识符、注释保持原项目语言）。 ## 项目概述 SPlayer-Next 是基于 **Electron + Vue 3 + TypeScript** 的桌面音乐播放器，后继 SPlayer，搭配 **Rust NAPI-RS** 原生模块做音频解码
No other project uses it yet
jaegertracingCopilot instructionsjaegertracing/jaeger-ui/.github/copilot-instructions.md
Copilot Review Instructions ## Core principle Prefer silence over uncertainty. A review comment has a cost — it demands the author's attention, may trigger another round, and can obscure the comments
skforecastCopilot instructionsskforecast/skforecast/.github/copilot-instructions.md
deep learning tests do not need to pass unless you work on that code. When they are needed (e.g. `ForecasterRnn` or foundation models), set `SKFORECAST_CLOUD
No other project uses it yet
UnpackerrCopilot instructionsUnpackerr/unpackerr/.github/copilot-instructions.md
folder tracker. HTTP handlers validate input and hand mutations to that goroutine through `onMainLoop`. Review with that model in mind; the items below have been raised and rejected before. ## Concurrency
No other project uses it yet
django-componentsCopilot instructionsdjango-components/django-components/.github/copilot-instructions.md
Development Workflow 1. Install dependencies: `uv sync --group dev` 2. Make changes to source code in `src/django_components/` 3. Run tests: `python -m pytest tests/test_component.py` (or specific test files
AzureADCopilot instructionsAzureAD/microsoft-authentication-library-for-dotnet/.github/copilot-instructions.md
Code Review Rules These rules apply to Copilot code review. Read all rules before commenting. ## Mandatory repository-wide review skill - Before reviewing any pull request, use the `msal-code-review
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.
