How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
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
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
MicrosoftCopilot instructionsmicrosoft/vscode/.github/copilot-instructions.md
valid-layers-check` only when a change may affect module layering. ## Coding Guidelines ### Indentation We use tabs, not spaces. ### Naming Conventions - Use PascalCase for `type` names - Use PascalCase for `enum
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
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
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.
