How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
affaan-mCopilot instructionsaffaan-m/ECC/.github/copilot-instructions.md
coding** — for features larger than a single function, outline phases and dependencies first. 3. **Test-driven** — write the test before the implementation; target 80%+ coverage. 4. **Review before committing** — check
MicrosoftCopilot instructionsmicrosoft/vscode/extensions/copilot/.github/copilot-instructions.md
proposed APIs for chat, language models, and editing - **ESBuild**: Bundling and compilation - **Vitest**: Unit testing framework - **Python**: For notebooks integration and ML evaluation scripts ## Validating changes Choose validation based
MicrosoftCopilot instructionsmicrosoft/vscode/.github/copilot-instructions.md
organized into key architectural layers: ### Root Folders - `src/`: Main TypeScript source code with unit tests in `src/vs/*/test/` folders - `build/`: Build scripts and CI/CD tools - `extensions/`: Built-in extensions that
Hugging FaceCopilot instructionshuggingface/transformers/.github/copilot-instructions.md
inherit from base classes in the root `/src/transformers` directory. - `/tests`: This contains the core test classes for the library. These are usually inherited rather than directly run. - `/models`: Tests
DietrichGebertCopilot instructionsDietrichGebert/ponytail/.github/copilot-instructions.md
thing that fails if the logic breaks (an assert-based demo/self-check or one small test file; no frameworks, no fixtures). Trivial one-liners need no test
MicrosoftCopilot instructionsmicrosoft/PowerToys/.github/copilot-instructions.md
PowerToys AI contributor guidance
MicrosoftCopilot instructionsmicrosoft/TypeScript/.github/copilot-instructions.md
pipelines. Most compiler development takes place in `tsc/internal`, and most behaviors can be tested via compiler tests. Most development on the codebase is in Go. Standard Go commands and practices
SupabaseCopilot instructionssupabase/supabase/.github/copilot-instructions.md
every PR - **Typos or spelling** — Automated typo detection runs on every PR - **Missing tests for trivial changes** — Handled by topic-specific test instructions - **Import ordering or grouping** — Handled by linter
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.
