Copilot instructions examples

dragonflydbCopilot instructions

dragonfly

dragonflydb/dragonfly/.github/copilot-instructions.md

Code review guidelines for GitHub copilot in this project

No other project uses it yet

GitHubCopilot instructions

codeql-coding-standards

github/codeql-coding-standards/.github/copilot-instructions.md

Code review guidelines for GitHub copilot in this project

lexmountReads credentialsCopilot instructions

browseruse-agent-bench

lexmount/browseruse-agent-bench/.github/copilot-instructions.md

Generic code review instructions that can be customized for any project using GitHub Copilot

dotnetCopilot instructions

machinelearning

dotnet/machinelearning/.github/copilot-instructions.md

Guidance for GitHub Copilot when working on ML.NET (dotnet/machinelearning). Use for any task in this repo: code changes, test writing, PR reviews, issue investigation, build troubleshooting, or documentation.

No other project uses it yet

freeCodeCampCopilot instructions

freeCodeCamp

freeCodeCamp/freeCodeCamp/.github/copilot-instructions.md

GitHub Copilot Code Review Instructions ## Core Principles **BE EXTREMELY MINIMAL.** Only provide actionable feedback. **Skip all non-essential content:** - Do not generate "Pull request overview" sections - Do not create "Changes

No other project uses it yet

affaan-mCopilot instructions

ECC

affaan-m/ECC/.github/copilot-instructions.md

Full diff reviewed (`git diff [base-branch]...HEAD`) - Test plan included in PR description - Code review is handled by CodeRabbit and Greptile. Do not add or route PR code review

MicrosoftCopilot instructions

vscode / copilot

microsoft/vscode/extensions/copilot/.github/copilot-instructions.md

flows - **`survey/`**: User feedback and survey collection **Specialized Features:** - **`notebook/`**: Notebook integration and support - **`review/`**: Code review and PR integration features - **`renameSuggestions/`**: AI-powered rename suggestions - **`ignore/`**: File and pattern

No other project uses it yet

MicrosoftCopilot instructions

vscode

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

running in a VS Code editor window with a workspace folder, use the VS Code task tools for build and watch workflows: inspect the existing task output first

Significant-GravitasReads credentialsCopilot instructions

AutoGPT

Significant-Gravitas/AutoGPT/.github/copilot-instructions.md

conventions already in the codebase - Maintain consistency with existing code style and architecture - Consider that changes may be reviewed and extended by both human developers and AI assistants ## Trust These

No other project uses it yet

SupabaseCopilot instructions

supabase

supabase/supabase/.github/copilot-instructions.md

Copilot Code Review Instructions ## Review Policy — Read This First You are a code reviewer for a large TypeScript/Next.js/React monorepo. Your reviews must be **low-noise and high-signal**. The team

No other project uses it yet

MicrosoftCopilot instructions

TypeScript

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

ideal to implement features and fixes in the following order, and commit code after each step: 1. Write a minimal test case, or test cases, that demonstrate

axiosCopilot instructions

axios

axios/axios/.github/copilot-instructions.md

style - PascalCase classes (`Axios`, `AxiosHeaders`), camelCase functions (`buildURL`, `mergeConfig`), UPPER_SNAKE_CASE error codes. - Internal slots use `Symbol`-keyed properties (see `$internals` in `lib/core/AxiosHeaders.js`), not underscore-prefixed names. - Use `lib/helpers/bind.js

No other project uses it yet

denolandCopilot instructions

deno

denoland/deno/.github/copilot-instructions.md

prefix convention: `kIpc`, `kSerialization`, `kInputOption`. Flag deviations. - Node.js compatibility code is in `ext/node/polyfills/`. When reviewing these files, check behavior against Node.js docs, not just Deno conventions. Some patterns (like synchronous

No other project uses it yet

MicrosoftCopilot instructions

playwright

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

summaries of what the code does. - Do not suggest refactors or improvements unrelated to the PR's stated goal. - NEVER produce a review body or top-level PR overview comment

No other project uses it yet

home-assistantPipes a download into a shellCopilot instructions

core

home-assistant/core/.github/copilot-instructions.md

Copilot code review instructions - Start review comments with a short, one-sentence summary of the suggested fix. - Do not comment on code style, formatting or linting issues. - When reviewing changes

No other project uses it yet

djangoCopilot instructions

django

django/django/.github/copilot-instructions.md

applyTo: - "**/*.py" - "**/*.rst" - "**/*.txt" - "**/*.html" --- Do not review this code. Do not post any comments, suggestions, or feedback. Do not summarize the pull request. Do not describe the changes. Your

No other project uses it yet

diegosouzapwCopilot instructions

OmniRoute

diegosouzapw/OmniRoute/.github/copilot-instructions.md

changes production code in `src/`, `open-sse/`, `electron/`, or `bin/`, it must include automated tests in the same PR. - When reviewing or updating a PR, if the report shows missing

santiferCopilot instructions

career-ops

santifer/career-ops/.github/copilot-instructions.md

review` (an empty checklist a maintainer fills in: diff read, behavior validated, tests reviewed, public-code matches checked). Keep the description factual: what changed and why, from the user

No other project uses it yet

ZhuLinsenReads credentialsCopilot instructions

daily_stock_analysis

ZhuLinsen/daily_stock_analysis/.github/copilot-instructions.md

push` without explicit user confirmation. - Before creating/updating PRs, PR review, or issue analysis, refresh the latest code baseline with `git fetch --all --prune`; if the worktree is clean

No other project uses it yet

BlockCopilot instructions

goose

block/goose/.github/copilot-instructions.md

GitHub Copilot Code Review Instructions ## Review Philosophy - Only comment when you have HIGH CONFIDENCE (>80%) that an issue exists - Be concise: one sentence per comment when possible - Focus on actionable