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.
javalinCopilot instructionsjavalin/javalin/.github/copilot-instructions.md
HTTP request handling` - `[workflow] Update GitHub Actions dependencies` - `[deps] Bump Jackson version to fix security issue` - `[static-files] Fix path decoding for special characters` - `[context] Add method to disable response
Steady20 mentions in 2 weeks
No other project uses it yet
kyvernoCopilot instructionskyverno/kyverno/.github/copilot-instructions.md
Kyverno is a Kubernetes-native policy engine for security, compliance, and governance via admission control and background scans. This file is instructions for *how* to review here — facts about specific
No other project uses it yet
chefCopilot instructionschef/chef/.github/copilot-instructions.md
ensure no regressions - Verify code quality and adherence to Ruby standards - Check for any security implications - Validate functionality across different environments ### 6. Documentation - Update relevant documentation - Add inline code comments
No other project uses it yet
smartcontractkitCopilot instructionssmartcontractkit/chainlink/.github/copilot-instructions.md
with enough context for callers to inspect and operators to diagnose? 5. **Security**: Is untrusted input validated at the trust boundary? Do secrets stay out of logs, errors, and responses
No other project uses it yet
opencartReads credentialsCopilot instructionsopencart/opencart/.github/copilot-instructions.md
Helper Functions Use `oc_*` prefixed global functions from `system/helper/`: ```php oc_token(32); // Generate secure token oc_strlen($string); // Multibyte-safe strlen oc_substr($string, 0, 100); // Multibyte-safe substr
No other project uses it yet
go-gitCopilot instructionsgo-git/go-git/.github/copilot-instructions.md
that explain the risk and suggest a concrete fix or follow-up. - Flag correctness, security, compatibility, or maintainability issues over minor style preferences. - Avoid low-value style comments unless they
No other project uses it yet
kubernetes-sigsCopilot instructionskubernetes-sigs/headlamp/.github/copilot-instructions.md
include `Fixes #NN` in commit messages. ## Review Priorities - Prioritize correctness, behavior regressions, security risks, and missing tests. - Keep findings concrete and actionable, and include file and line references when possible
No other project uses it yet
condaCopilot instructionsconda/conda/.github/copilot-instructions.md
suggest refactors, performance improvements, or alternative implementations. - Do not flag potential bugs, security issues, or logic errors as part of a review. - Do not provide summaries or overviews
No other project uses it yet
krausestCopilot instructionskrausest/js-framework-benchmark/.github/copilot-instructions.md
available via npm and github. If not report a warning. 5. Perform a security audit especially regarding supply chain attacks. To clarify: Malicious packages are inacceptable, even severe security issues
No other project uses it yet
projectcalicoCopilot instructionsprojectcalico/calico/.github/copilot-instructions.md
Overview This is the main **Project Calico** repository - an open-source container networking and security solution. Calico provides data plane choice (eBPF, standard Linux, Windows, VPP), advanced security features
No other project uses it yet
jokob-skCopilot instructionsjokob-sk/NetAlertX/.github/copilot-instructions.md
ROLE: NETALERTX ARCHITECT & STRICT CODE AUDITOR You are a cynical Security Engineer and Core Maintainer of NetAlertX. Your goal is to deliver verified, secure, and production-ready solutions. ### MANDATORY BEHAVIORAL
1 project uses a version of this
go-co-opCopilot instructionsgo-co-op/gocron/.github/copilot-instructions.md
config compatibility varies) ## Common Tasks ### Repository Structure ``` . ├── README.md # Main documentation ├── CONTRIBUTING.md # Contribution guidelines ├── SECURITY.md # Security policy ├── Makefile # Build automation ├── go.mod # Go module definition ├── .github/ # GitHub workflows and configs ├── .golangci.yaml # Linting
No other project uses it yet
elementorCopilot instructionselementor/elementor/.github/copilot-instructions.md
copilot-instructions/javascript-frontend.md) - [TypeScript & React](copilot-instructions/typescript-react.md) - [Testing Best Practices](copilot-instructions/testing.md) - [Security & Validation](copilot-instructions/security.md) --- ## Critical Partner Mindset Do not affirm my statements or assume
No other project uses it yet
openmediavaultCopilot instructionsopenmediavault/openmediavault/.github/copilot-instructions.md
conventions outlined below to ensure consistency and maintainability. Pay particular attention to the [Security Checks](#security-checks) section. ## General Conventions - All code must adhere to the standards defined
No other project uses it yet
AethersailorCopilot instructionsAethersailor/Custom_OpenClash_Rules/.github/copilot-instructions.md
text rules overwrite config subconverter shell substore readme wiki docs validation pages sync deps security cdn workflow repo ``` Use these spellings consistently. Do not invent singular, plural, or synonymous variants
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/GSL/.github/copilot-instructions.md
system (3.14+) - Google Test for unit testing - Support for multiple compilers (MSVC, GCC, Clang) ## Security Considerations - Bounds checking is a core principle - enforce it consistently - Design for safety while minimizing
No other project uses it yet
CodeWithCJReads credentialsCopilot instructionsCodeWithCJ/SparkyFitness/.github/copilot-instructions.md
React 18 + TypeScript + Vite (`src/`) - **Backend**: Node.js/Express (`SparkyFitnessServer/`) - **Database**: PostgreSQL with Row Level Security (RLS) - **UI**: Tailwind CSS + shadcn/ui components - **State**: React Context + TanStack Query - **AI**: Multi-provider support
No other project uses it yet
glpi-projectCopilot instructionsglpi-project/glpi/.github/copilot-instructions.md
already-imported ones; new dependencies must be GPLv3+ compatible. - Always ensure generated code is secure and free from vulnerabilities. - Do not ask clarification questions unless a real technical choice must
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/agent-governance-toolkit/.github/copilot-instructions.md
packages or modules that change the repo structure - Cross-cutting changes spanning 3+ packages - Security model changes (identity, trust, policy engine) - Breaking API changes to public interfaces - New framework integrations
No other project uses it yet
vllm-projectCopilot instructionsvllm-project/semantic-router/.github/copilot-instructions.md
DOMAIN=...` or `make verify PROFILE=...`; use `make harness-check` for harness/workflow edits. Prioritize correctness, security, public contracts, missing behavior tests, and real dependency boundaries. Numeric size metrics are advisory: recommend
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.
