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.
freeCodeCampCopilot instructionsfreeCodeCamp/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 instructionsaffaan-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
Steady32 mentions in 2 weeks
2 projects use a version of this
MicrosoftCopilot instructionsmicrosoft/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 instructionsmicrosoft/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 instructionsSignificant-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
Steady3 mentions in 2 weeks
No other project uses it yet
SupabaseCopilot instructionssupabase/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
Steady6 mentions in 2 weeks
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/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 instructionsaxios/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 instructionsdenoland/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
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.
