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.
celeryCopilot instructionscelery/celery/.github/copilot-instructions.md
prompts for the human reviewer. - Keep comments atomic and actionable; include the bottom-line ask and, when helpful, a suggested next step. - Avoid prescriptive code changes unless asked; prefer intent
No other project uses it yet
koodo-readerCopilot instructionskoodo-reader/koodo-reader/.github/copilot-instructions.md
Koodo Reader – Code Review Standards ## Security Critical Issues - Validate all IPC arguments from the renderer before filesystem, DB, or shell operations - Never log tokens, passwords, or full book-file paths
No other project uses it yet
valkey-ioCopilot instructionsvalkey-io/valkey/.github/copilot-instructions.md
Valkey Project Instructions You are an expert code reviewer for the Valkey project. Provide helpful, constructive feedback on code quality, safety, and adherence to project standards. ## 1. Review Tone & Focus
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/winget-cli/.github/copilot-instructions.md
bodies; open a pull request or link a branch when code is available. - Before opening a pull request, review `CONTRIBUTING.md`, follow the PR template, keep the change focused, and summarize
No other project uses it yet
BabylonJSCopilot instructionsBabylonJS/Babylon.js/.github/copilot-instructions.md
warnings omitted by the normal quiet lint commands) - **Unit tests**: `npm run test:unit` ## Code review When reviewing a PR or reviewing changes on the current branch, use the `code
Steady3 mentions in 2 weeks
No other project uses it yet
daprCopilot instructionsdapr/dapr/.github/copilot-instructions.md
Code compiles: `make build` - [ ] Unit tests pass: `make test` - [ ] Linter passes: `make lint` - [ ] New code has test coverage - [ ] All new files have Apache 2.0 license header - [ ] Commits are signed
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/typescript-go/.github/copilot-instructions.md
across commits, but be sure to update baselines every time so that reviewers can measure progress. ## Code Porting Reference The code in `internal` is ported from the code in `_submodules/TypeScript
lvglCopilot instructionslvgl/lvgl/.github/copilot-instructions.md
LVGL Code Review Instructions LVGL is an embedded C99 graphics library for MCUs, MPUs, and simulators. Code must be portable, memory-efficient, and bare-metal safe. ## Critical Issues (always flag
No other project uses it yet
docmirrorCopilot instructionsdocmirror/dev-sidecar/.github/copilot-instructions.md
root with `pnpm lint:fix`. - If `pnpm lint` or `pnpm lint:fix` fails, review the reported errors and manually fix the files indicated by the linter, then
No other project uses it yet
temporalioCopilot instructionstemporalio/temporal/.github/copilot-instructions.md
Code Guidelines These rules apply when authoring or reviewing code; the Behavior Review and Review Feedback Style sections apply only when reviewing code. Express each rule as a concise, direct
No other project uses it yet
marimo-teamCopilot instructionsmarimo-team/marimo/.github/copilot-instructions.md
Code Review Process 1. If the PR seems AI-generated, you should request the contributor to: - Provide screenshots of the fixed output (if possible) - Check if it satisfies edge cases
No other project uses it yet
jaegertracingCopilot instructionsjaegertracing/jaeger/.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
No other project uses it yet
oxc-projectCopilot instructionsoxc-project/oxc/.github/copilot-instructions.md
Copilot Review Instructions When reviewing pull requests in this repository: - Do not guess or infer compiler errors. Only report them when supported by actual compiler diagnostics. - Treat files inside
No other project uses it yet
dotnetCopilot instructionsdotnet/maui/.github/copilot-instructions.md
Guidance for GitHub Copilot when working on the .NET MAUI repository.
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
Steady6 mentions in 2 weeks
No other project uses it yet
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
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
No other project uses it yet
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
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.
