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
bytedanceCopilot instructionsbytedance/deer-flow/.github/copilot-instructions.md
make install ``` ### B. Backend CI-equivalent validation Run from `backend/`: ```bash make lint make test ``` Validated results: - `make lint`: pass (`ruff check .`) - `make test`: pass (`277 passed, 15 warnings
rtk-aiCopilot instructionsrtk-ai/rtk/.github/copilot-instructions.md
status rtk git status git log -10 rtk git log -10 cargo test rtk cargo test cargo clippy --all-targets rtk cargo clippy --all-targets grep -r "pattern
headroomlabs-aiCopilot instructionsheadroomlabs-ai/headroom/.github/copilot-instructions.md
Behavior Proof" with environment, exact commands or steps, observed result, and what was not tested. 3. Be strict about contributor verification: missing tests, missing runtime evidence, or placeholder PR text
career-ops-hqCopilot instructionscareer-ops-hq/career-ops/.github/copilot-instructions.md
were asked to reproduce a bug, brief a pull request, write or fix a test, re-sync a translation, find stale documentation, or make any change to the code (this
diegosouzapwCopilot instructionsdiegosouzapw/OmniRoute/.github/copilot-instructions.md
OmniRoute PR and Coverage Instructions - Treat `npm run test:coverage` as a required gate for PR work. - The repository minimum is `60%` for statements, lines, functions, and branches
ClineCopilot instructionscline/cline/.github/copilot-instructions.md
gRPC-like protocol over VS Code message passing. Schemas in `proto/`. - **MCP**: `src/services/mcp/McpHub.ts`. ## Build & Test (Critical — non-obvious commands) - **Build**: `bun run compile` — NOT `bun run build`. - **Watch
mvanhornCopilot instructionsmvanhorn/last30days-skill/.github/copilot-instructions.md
specific additions. See AGENTS.md for the shared cross-tool governance layer. # Copilot-specific guidance ## Test generation - Prefer unittest.TestCase for generated tests to match the existing test suite. - Mock external calls
MicrosoftCopilot instructionsmicrosoft/autogen/.github/copilot-instructions.md
seconds. poe pyright # Takes 41 seconds. Set timeout to 120+ seconds. # Individual package testing (core package example) poe --directory ./packages/autogen-core test # Takes 10 seconds. Set timeout to 60+ seconds. # Documentation
aaif-gooseCopilot instructionsaaif-goose/goose/.github/copilot-instructions.md
What Our CI Checks (`.github/workflows/ci.yml`) **Rust checks:** - `cargo fmt --check` - Code formatting (rustfmt) - `cargo test --jobs 2` - All tests - `cargo clippy --all-targets -- -D warnings` - Linting (clippy) **Desktop app checks
ToolJetCopilot instructionsToolJet/ToolJet/.github/copilot-instructions.md
only. No Redux/MobX/Recoil. - Use `shallow` comparison in `useStore` when selecting objects/arrays. Flag missing `shallow`. ## Tests Rules: `.github/instructions/frontend-tests.instructions.md`. How to write one: `frontend/src/test/README.md`. Reject any spec that would still pass against
HashiCorpCopilot instructionshashicorp/vault/.github/copilot-instructions.md
style, package organization, error handling, and idiomatic patterns - **[golang_tests.instructions.md](instructions/generic/golang_tests.instructions.md)**: Best practices for writing tests in Go, including table-driven tests, test structure, and integration testing ### Ember.js UI Development - **[ember_general.instructions.md
MicrosoftCopilot instructionsmicrosoft/WSL/.github/copilot-instructions.md
Linux-side WSL components - `src/shared/` — Shared code between Windows and Linux - `test/windows/` — Windows-based tests (TAEF framework) - `test/linux/unit_tests/` — Linux unit test suite - `doc/` — Documentation source (MkDocs) - `tools/` — Build and deployment
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.
