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.
open-edge-platformCopilot instructionsopen-edge-platform/anomalib/.github/copilot-instructions.md
missing required quality gates: tests, docs, changelog, or pre-commit checks. - Touches workflow or security-sensitive files (`SECURITY.md`, `.github/`, deployment configs) without appropriate scrutiny. **Quality expectations:** - Contributors run `pre-commit
Steady2 mentions in 2 weeks
No other project uses it yet
apacheCopilot instructionsapache/pinot/.github/copilot-instructions.md
appropriate collection types based on access patterns (e.g., ArrayList for iteration, HashMap for lookups). ## Security Guidelines - Never log sensitive information like passwords, API keys, or personally identifiable data. - Validate
No other project uses it yet
Microsoft AzureCopilot instructionsAzure/azure-sdk-for-net/.github/copilot-instructions.md
specific rules augment rather than replace the normal open-ended review for bugs, security, correctness, reliability, and maintainability
No other project uses it yet
inngestCopilot instructionsinngest/inngest/.github/copilot-instructions.md
Vendor dependencies make vendor # Run specific Go test go test ./pkg/execution -run TestFunctionName -v ``` ## Security Considerations - Never commit secrets or credentials - Use environment variables for sensitive configuration - UI uses pnpm
No other project uses it yet
codeigniter4Copilot instructionscodeigniter4/CodeIgniter4/.github/copilot-instructions.md
priorities Prioritize actionable findings involving: - incorrect behavior or an unhandled edge case; - backward compatibility; - security, input validation, and context-appropriate output escaping; - request-specific state leaking through globals, static properties
Steady9 mentions in 2 weeks
No other project uses it yet
gpustackCopilot instructionsgpustack/gpustack/.github/copilot-instructions.md
Keep review feedback specific and actionable, and cite the file and line. Report correctness, security, data-loss, and regression risks; do not report stylistic preferences already enforced by formatters
Steady5 mentions in 2 weeks
No other project uses it yet
btraceioCopilot instructionsbtraceio/btrace/.github/copilot-instructions.md
concurrency, existing BTrace APIs - **No temporary files in repo**: Use `/tmp` for scratch work - **Security**: Never commit secrets; avoid introducing vulnerabilities ## Example BTrace Script Pattern ```java package example; import static
No other project uses it yet
CountlyCopilot instructionsCountly/countly-server/.github/copilot-instructions.md
package.json # Plugin metadata ├── install.js # Installation hook └── tests.js # Plugin tests ``` ## Backend Development Checklist ### API Endpoint Security (REQUIRED) **Every endpoint must use validation** from `api/utils/rights.js`: ```javascript const { validateRead, validateCreate, validateUpdate, validateDelete } = require
No other project uses it yet
tuistCopilot instructionstuist/tuist/.github/copilot-instructions.md
performance bottlenecks - Check for efficient use of resources - Verify no unnecessary computations or allocations ### Security - Review for potential security vulnerabilities - Ensure no hardcoded secrets or sensitive information - Check proper input
Steady10 mentions in 2 weeks
No other project uses it yet
dependabotCopilot instructionsdependabot/dependabot-core/.github/copilot-instructions.md
core classes are implemented and follow the inheritance patterns from `dependabot-common`. ## Integration Points ### Security Updates Handle `SECURITY_ADVISORIES` for vulnerability-driven updates that target minimum safe versions rather than
No other project uses it yet
prettierCopilot instructionsprettier/prettier-vscode/.github/copilot-instructions.md
using the Extension Development Host ## Code Review Guidelines When reviewing pull requests, focus on: ### Security - No hardcoded secrets or credentials - Workspace Trust is respected when resolving modules from untrusted workspaces
leokhoaCopilot instructionsleokhoa/laragon/.github/copilot-instructions.md
templates ├── www/ # Default web root directory ├── README.md # Project documentation ├── CHANGELOG.md # Version history └── SECURITY.md # Security policy ``` ## Key Features - **Portable**: Entire environment can be moved between Windows machines - **Auto-configuration**: Services
MicrosoftCopilot instructionsmicrosoft/azurelinux/.github/copilot-instructions.md
keeps maintenance overhead low and makes it easier to pull in new versions and security updates from upstream. While AZL derives from Fedora, it is also an enterprise focused distro
No other project uses it yet
vitali87Copilot instructionsvitali87/code-graph-rag/.github/copilot-instructions.md
pull requests: - Only leave comments for critical, major, or high-severity issues: logic bugs, security vulnerabilities, data loss or corruption, race conditions, and breaking API changes. - Do NOT comment
Steady19 mentions in 2 weeks
No other project uses it yet
dubzzzCopilot instructionsdubzzz/fast-check/.github/copilot-instructions.md
configuration files - 🎨 Improve structure/format of the code - 🔥 Remove code or files - 🚀 Deploy stuff - 🔒️ Fix security or privacy issues - ⬆️ Upgrade dependencies - ⬇️ Downgrade dependencies - 📦 Add or update compiled files or packages
Steady3 mentions in 2 weeks
No other project uses it yet
harvesterCopilot instructionsharvester/harvester/.github/copilot-instructions.md
conventions outlined below to ensure consistency and maintainability. Pay particular attention to the [Security Checks](#security-checks) section below. ## Go Conventions - Go version: see `go.mod` (`go` directive) - All code must
baomidouCopilot instructionsbaomidou/dynamic-datasource/.github/copilot-instructions.md
configuration properties belong in `DynamicDataSourceProperties` and must be documented at https://doc.xiuceyun.cn (separate repository). - Security findings are **not** public issues: see `SECURITY.md
No other project uses it yet
nginxCopilot instructionsnginx/kubernetes-ingress/.github/copilot-instructions.md
before `nic-code-review`. Never load it for local reviews | --- ## Key Invariants - **NGINX config security**: Run `containsDangerousChars()` on every user-provided string that reaches NGINX config (dangerous: `;`, `{`, `}`, `\n`, `\r`, `$`, backtick
xvzcCopilot instructionsxvzc/spoofdpi/.github/copilot-instructions.md
Senior Go Backend Engineer and Security Auditor. Review the following code with a strict focus on **CRITICAL BUGS** and **STABILITY ISSUES**. **🚫 IGNORE the following (Do NOT report):** - Coding style, formatting
dmno-devReads credentialsCopilot instructionsdmno-dev/varlock/.github/copilot-instructions.md
Copilot PR code review (security) **Scope:** Focus on **code** security. Copilot does not review dependency manifests or lockfiles; rely on Dependabot, CodeQL, and the dependency-review workflow for supply chain
Steady23 mentions in 2 weeks
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.
