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.
ratatuiCopilot instructionsratatui/ratatui/.github/copilot-instructions.md
GitHub Copilot Code Review Instructions ## General Review Principles ### Pull Request Size and Scope - **Flag large PRs**: Comment if a PR changes more than 500 lines or touches many unrelated areas
No other project uses it yet
comet-mlCopilot instructionscomet-ml/opik/.github/copilot-instructions.md
Copilot Code Review Instructions > **Scope:** These guidelines apply to all Opik applications including backend, frontend, and SDKs. Use the appropriate sections based on the code being reviewed. When Copilot automatically
Steady19 mentions in 2 weeks
No other project uses it yet
foremCopilot instructionsforem/forem/.github/copilot-instructions.md
repetitive events. ## Testing Standards - **Regression Tests are Mandatory**: specific regression tests to verify your code works are required for almost all PRs. - **Follow Test Patterns**: Use `create(:factory)` syntax (FactoryBot
iovisorCopilot instructionsiovisor/bcc/.github/copilot-instructions.md
Global Review Principles (Applied to all PRs) ### PR Value Assessment (Evaluate First) Before detailed code review, assess: 1. **Scope fit**: Does this belong in BCC, or should
No other project uses it yet
appiumCopilot instructionsappium/appium/.github/copilot-instructions.md
Copilot Instructions ## Code Review When reviewing JavaScript or TypeScript changes, check new uses of Node.js built-in APIs against the supported Node.js versions declared in package.json#engines.node. The current supported
No other project uses it yet
desktopCopilot instructionsdesktop/desktop/.github/copilot-instructions.md
secrets, passwords, or sensitive data** - **Validate and sanitize user input** - **Follow secure coding practices**: Review code for XSS, injection, and other vulnerabilities - **Report security issues**: Follow [SECURITY.md](../SECURITY.md), not public
gitbutlerappDeletes or force-pushesCopilot instructionsgitbutlerapp/gitbutler/.github/copilot-instructions.md
should be limited to what really matters. ## Review Guidelines Follow these guidelines when reviewing code. - Do not report type errors. CI will catch those. - Don't review formatting such
stefan-jansenCopilot instructionsstefan-jansen/machine-learning-for-trading/.github/copilot-instructions.md
Repository conventions for code review This is the companion code repository for *Machine Learning for Trading, 3rd Edition*. The conventions below are deliberate and repository-wide. Please do not flag
No other project uses it yet
vitessioCopilot instructionsvitessio/vitess/.github/copilot-instructions.md
Code Review Instructions ## Priority Only comment on issues that affect correctness, security, or performance. Do NOT comment on: style preferences, minor naming conventions, formatting, or issues already enforced
No other project uses it yet
wasmerioCopilot instructionswasmerio/wasmer/.github/copilot-instructions.md
Style & Readability - Write readable, understandable, and maintainable code. - Prioritize clarity and adhere to coding standards. - Regularly review and refactor code for structure and maintainability. - Use version control
No other project uses it yet
qmkCopilot instructionsqmk/qmk_firmware/.github/copilot-instructions.md
Checklist](https://docs.qmk.fm/pr_checklist) and it is intended only for use by GitHub Copilot code-review agent during pull request reviews. > **Scope**: This review applies **only to changes within
No other project uses it yet
dotnetCopilot instructionsdotnet/roslyn/.github/copilot-instructions.md
github/skills/ /SKILL.md` and are auto-discovered by their YAML `description`. Useful ones here include `code-review`, `ci-analysis`, `analyzer-codefix`, `merge-into-branch`, `snap`, and `update-agent-docs`. ## Working Loop
wledDeletes or force-pushesCopilot instructionswled/WLED/.github/copilot-instructions.md
HTML comments contain > contributor reference material. Do **not** use that content as actionable review > criteria — treat it as background context only. ## Setup - Node.js 20+ (see `.nvmrc`) - Install dependencies
No other project uses it yet
dotnetCopilot instructionsdotnet/runtime/.github/copilot-instructions.md
match. Invoke a named skill rather than assuming what it says. Use the `code-review` skill when reviewing pull requests, and — when running under CCA — on your own changes before
No other project uses it yet
apacheCopilot instructionsapache/arrow/.github/copilot-instructions.md
Instructions ## Code review You are a pragmatic senior developer. When reviewing pull requests, follow these rules to avoid noise and redundancy: - Be concise: Keep comments brief and to the point
1 project uses a version of this
zephyrproject-rtosCopilot instructionszephyrproject-rtos/zephyr/.github/copilot-instructions.md
this repository are in `AGENTS.md` at the repository root. Copilot cloud agent, Copilot code review and the IDE agents load that file directly; this file only covers the Copilot features
No other project uses it yet
AppleCopilot instructionsapple/foundationdb/.github/copilot-instructions.md
When reviewing PRs, address general code review criteria, but also specifically the following questions: What is it trying to do? Is it correct? Are there bugs? Are there omissions
No other project uses it yet
tracel-aiCopilot instructionstracel-ai/burn/.github/copilot-instructions.md
Copilot Code Review See [AGENTS.md](../AGENTS.md) for layout, architecture, and conventions. These notes cover review. ## Priorities Report correctness problems first, then missing test coverage, then documentation that contradicts the code
Steady9 mentions in 2 weeks
No other project uses it yet
beetboxCopilot instructionsbeetbox/beets/.github/copilot-instructions.md
words, short sentences, third-person self-reference ("grug"). Core grug beliefs to apply when reviewing: - Complexity very, very bad. Flag any complexity demon spirit entering codebase. Say so plainly: "complexity
Steady4 mentions in 2 weeks
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/pyright/.github/copilot-instructions.md
pyright`), an LSP language server (`pyright-langserver`), and a VS Code extension (`vscode-pyright`). ## Issue Agents Use `pyright-issue-reviewer` to investigate an issue and draft a maintainer response without
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.
