Copilot instructions examples

BetterThanTomorrowCopilot instructions

calva

BetterThanTomorrow/calva/.github/copilot-instructions.md

with the REPL API](https://github.com/BetterThanTomorrow/calva/issues/3244)`). * After changing code, run CodeScene's `code_health_review` on the changed files. If Code Health drops, fix the issues, run the review

zereightCopilot instructions

gitlab-mcp

zereight/gitlab-mcp/.github/copilot-instructions.md

Root cause analysis, build fixes | Full access | | @verifier | Evidence-based completion checks | Test runner | | @code-reviewer | Code quality, spec compliance | READ-ONLY | | @security-reviewer | OWASP vulnerability detection | READ-ONLY | | @test

No other project uses it yet

DynamoDSCopilot instructions

Dynamo

DynamoDS/Dynamo/.github/copilot-instructions.md

analyzer warnings for XML-related vulnerabilities (CA2327, CA2329, CA2330, CA2328) are treated as errors - Code changes should contain no files larger than 50 MB (validated by the `check_file_size.yml` workflow) ## Agent

MicrosoftCopilot instructions

maker.js

microsoft/maker.js/.github/copilot-instructions.md

repository. ## Before Committing Always: 1. Review the files being committed with `git status` or `git diff --cached` 2. Ensure only source code, tests, and documentation are included 3. Check that

JurajNyiriCopilot instructions

HomeAssistant-Tapo-Control

JurajNyiri/HomeAssistant-Tapo-Control/.github/copilot-instructions.md

text until they agree. Keep changes small and reviewable. Do not make broad root-cause claims without verifying the current code and relevant dependencies. Disclose AI assistance in PR descriptions

MicrosoftDocsCopilot instructions

architecture-center

MicrosoftDocs/architecture-center/.github/copilot-instructions.md

produced the initial draft with minimal human authorship - `ai-usage: ai-assisted` – Human-directed, reviewed, and edited with AI support - Omit only for purely human-authored legacy content If missing

Microsoft AzureCopilot instructions

azure-functions-host

Azure/azure-functions-host/.github/copilot-instructions.md

General * Make only high-confidence suggestions when reviewing code changes. * Always use the latest version of C#, currently C# 13 features. * Never change global.json unless explicitly asked to. * Never change

igraphCopilot instructions

igraph

igraph/igraph/.github/copilot-instructions.md

Code review guidelines When performing a code review, keep in mind the following. ## Coding standards - Check that all values of integer type are represented as `igraph_int_t`, except

YoastCopilot instructions

wordpress-seo

Yoast/wordpress-seo/.github/copilot-instructions.md

/PULL_REQUEST_TEMPLATE.md). [`AGENTS.md`](../AGENTS.md) adds agent-behaviour guidance. If anything below contradicts these, prefer them. ## Review priorities ### PR hygiene - Every required section of the PR template must have content — no empty

apacheCopilot instructions

trafficserver

apache/trafficserver/.github/copilot-instructions.md

conventions that will not themselves cause CI failures but should still be followed in code reviews. **Formatting Rules:** - **Line length:** 132 characters maximum - **Indentation:** 2 spaces (never tabs) - **Braces:** Linux

MicrosoftCopilot instructions

snmalloc

microsoft/snmalloc/.github/copilot-instructions.md

dependency. - Design code to be easy to change, but do not add extension points or abstractions for hypothetical requirements. ## Change Discipline - Avoid over-engineering and review churn. Preserve names

No other project uses it yet

MicrosoftDeletes or force-pushesCopilot instructions

openvmm

microsoft/openvmm/.github/copilot-instructions.md

subtle and needs human review **Error handling across trust boundaries:** - Use `thiserror` for typed error enums at library/API boundaries and protocol-facing code - Use `anyhow` with `.context("...")` for application-level

QexoCopilot instructions

Qexo

Qexo/Qexo/.github/copilot-instructions.md

When performing a code review, respond in Simplified Chinese

scalityCopilot instructions

cloudserver

scality/cloudserver/.github/copilot-instructions.md

Code review instructions Repo context lives in [CLAUDE.md](../CLAUDE.md) — read it first. When reviewing a PR, analyze the changes against these criteria: | Area | What to check | | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Async error handling | uncaught

No other project uses it yet

featbitCopilot instructions

featbit

featbit/featbit/.github/copilot-instructions.md

package.json` as the source of truth for available scripts when implementing changes or reviewing CI. ```sh npm ci npm run dev # Vite development server npm run typecheck # TypeScript checks

GhostManagerReads credentialsCopilot instructions

Ghostwriter / copilot-instructions

GhostManager/Ghostwriter/.github/copilot-instructions/copilot-instructions.md

inactive-issues.yml** - Issue automation **No pre-commit hooks.** Quality enforced via: manual linting → CI checks → code review ## Common Issues 1. **Container "stuck":** Django won't restart → `docker compose -f local.yml

ocamlCopilot instructions

dune

ocaml/dune/.github/copilot-instructions.md

dune fmt # Auto-format code (run before committing) dune promote # Accept test output changes (ask user first) make dev # Full build (bootstraps if necessary) ``` ## Reviewing PRs Follow the repository review

CactiCopilot instructions

cacti

Cacti/cacti/.github/copilot-instructions.md

AppSec Mode) - **Context**: Cacti Takes Security Seriously consider the security implications when reviewing current and new code base - **Vulnerability Checks**: - **SQL Injection**: STRICTLY enforce prepared statements (`db_*_prepared`). Flag

besu-ethCopilot instructions

besu

besu-eth/besu/.github/copilot-instructions.md

Code Review - Focus on bugs, security issues, and correctness. Do not flag style nits. - Do not suggest adding comments, javadocs, or type annotations to unchanged code. - Do not flag naming

Microsoft AzureCopilot instructions

azure-sdk-for-go

Azure/azure-sdk-for-go/.github/copilot-instructions.md

entire module name. ## Generated Code — DO NOT suggest changes When performing a code review, if a file contains the header `// Code generated by Microsoft (R) Go Code Generator