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.
iovisorCopilot instructionsiovisor/ubpf/.github/copilot-instructions.md
linting (shellcheck) - C++ linting (cpplint) - Python linting (pylint) - Trailing whitespace and EOF fixes ## Copilot Code Review - When performing a pull request or normal code review for this repository
open-telemetryCopilot instructionsopen-telemetry/opentelemetry.io/.github/copilot-instructions.md
minutes. A lock-exact install with lifecycle scripts suppressed, followed by `ci:prepare` (reviewed Hugo-binary fetch, then `npm run prepare`: `get:submodule` and `_prepare:docsy`); the repo's [install
Ayush0ChaudharyReads credentialsCopilot instructionsAyush0Chaudhary/blurr/.github/copilot-instructions.md
minutes) 2. **Unit tests**: `./gradlew test` (wait for completion - 5-15 minutes) 3. **Code inspection**: Review any lint warnings in Android Studio ### Manual Testing Requirements When making changes to core
MicrosoftDeletes or force-pushesCopilot instructionsmicrosoft/vstest/.github/copilot-instructions.md
only changes (e.g. `.md` files) — these PRs go green in under a minute. - For code changes, check PR status within 15–20 minutes — the Windows build and tests finish first
dotCMSCopilot instructionsdotCMS/core/.github/copilot-instructions.md
value'; // NO! Use setInput() ``` ## Security Guidelines **⚠️ CRITICAL: Security violations are unacceptable and will fail code review.** ### Never Do These (Security Violations) ```java // ❌ NEVER: Hardcoded secrets or credentials String apiKey
serenedbCopilot instructionsserenedb/serenedb/.github/copilot-instructions.md
Assume code in review always complies and consistent with codestyle. You can be confused because we're using C++26, custom libc++, etc. In review focus on typo, bugs, test
meshtasticCopilot instructionsmeshtastic/Meshtastic-Apple/.github/copilot-instructions.md
tested, and include screenshots/videos when UI is affected (see `.github/pull_request_template.md`). - Self-review code before requesting review; comment complex areas. ## Deep Links The app registers the `meshtastic:///` URL scheme. Use `Router.route
openvinotoolkitDeletes or force-pushesCopilot instructionsopenvinotoolkit/model_server/.github/copilot-instructions.md
header leakage - Understanding of Bazel targets, build flags (`--//:distro`), and multi-stage Docker builds ## Code Review Instructions for PRs When analyzing a Pull Request, follow this protocol: 1. Follow
sunarya-thitoCopilot instructionssunarya-thito/shadcn_flutter/.github/copilot-instructions.md
update it, and how to reconstruct missing entries) - The API/class documentation for Dart/Flutter code (how to write comprehensive, analyzer-friendly docs) Keep responses concise, actionable, and consistent with the rules
chriswritescode-devCopilot instructionschriswritescode-dev/opencode-manager/.github/copilot-instructions.md
Copilot Code Review Instructions ## Technology Stack - **Monorepo**: pnpm workspace with backend, frontend, and shared packages - **Backend**: Bun runtime + Hono framework + Bun SQLite (bun:sqlite) - **Frontend**: React 19 + Vite 7 + Radix
ListenarrsReads credentialsCopilot instructionsListenarrs/Listenarr/.github/copilot-instructions.md
automated audiobook downloading and processing. ## Required Repository Context Before making code, dependency, workflow, or documentation changes, review and follow: - `CONTRIBUTING.md` - `BACKEND_ARCHITECTURE.md` - `.github/RULES.md` - `.github/AGENTS.md` - `.github/.cursorrules` Repository-specific guidance takes precedence over
yao-pkgCopilot instructionsyao-pkg/pkg/.github/copilot-instructions.md
checks pass before requesting review 5. **Small PRs**: Keep pull requests focused and reasonably sized 6. **Follow patterns**: Match existing code style and patterns 7. **Test cross-platform**: Test
matter-jsCopilot instructionsmatter-js/matter.js/.github/copilot-instructions.md
requests autonomously, and do not post comments on behalf of a user without their review. Additionally in this repository: never submit a bug report, root-cause claim, or fix whose
pnpCopilot instructionspnp/powershell/.github/copilot-instructions.md
issue → owning cmdlet → hypothesis | | `cmdlet-scaffolder` | New cmdlet from a sibling (produces a draft) | | `code-review` | Review the current change | VS Code also reads `.claude/agents/` in the Claude sub-agent
actionsCopilot instructionsactions/dependency-review-action/.github/copilot-instructions.md
Copilot Coding Agent Instructions Trust these instructions. Only search the codebase if information here is incomplete or found to be in error. ## Repository Overview **dependency-review-action** is a GitHub
SeagateCopilot instructionsSeagate/openSeaChest/.github/copilot-instructions.md
documentation - `subprojects/opensea-transport/CONTRIBUTING.md` - Transport library coding standards - `subprojects/opensea-operations/README.md` - Operations layer documentation - `subprojects/opensea-operations/CONTRIBUTING.md` - Operations library coding standards When reviewing or modifying code in subprojects, check their individual CONTRIBUTING.md files for library-specific
code-dot-orgCopilot instructionscode-dot-org/code-dot-org/.github/copilot-instructions.md
hard-coded in English, and later translated by localizeJS. When reviewing, new strings should be hard-coded in English
MicrosoftCopilot instructionsmicrosoft/OpenAIWorkshop/.github/copilot-instructions.md
Results**: Add review section to `tasks/todo.md` 6. **Capture Lessons**: Update `tasks/lessons.md` after corrections ## Core Principles - **Simplicity First**: Make every change as simple as possible. Impact minimal code. - **No Laziness**: Find
floci-ioCopilot instructionsfloci-io/floci-az/.github/copilot-instructions.md
Docker; do not introduce direct process execution ## Auth Review `floci-az.auth.mode` (`dev` or `strict`) is not read by any code today: every request is handled as in `dev`, and `SharedKeyAuthVerifier` accepts
zwave-jsCopilot instructionszwave-js/zwave-js/.github/copilot-instructions.md
claude/skills/` are symlinks to them for Claude Code. Always edit the canonical files, never the symlinks. - The rules for authoring, editing and reviewing device configuration files live in `.agents/instructions/config-files.md`. Read
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.
