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.
dotnetCopilot instructionsdotnet/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.
Steady10 mentions in 2 weeks
No other project uses it yet
williamcorrea23Reads credentialsCopilot instructionswilliamcorrea23/sap-router-skill/.github/copilot-instructions.md
SAP development orchestrator v5.0.0 — Karpathy command format (Think→Simplify→ Surgical→Verify), healthcheck guardian, self-learning router, caveman-compressed output default. 85 skills, 38 MCPs (+17 planned), 24 scripts. Multi-protocol: HTTP/OData/RFC/SOAP RFC/BDC. ZROUTER v5 REST gateway. Install pipeline: YDOWN→ZABAPGIT→ZSAPLINK. BDC engine: YFG_SBDC. Test suites: ZODATA_TEST_AUTOMATION_FGR. Use for any SAP task.
darknodebrosCopilot instructionsdarknodebros/EleSync/.github/copilot-instructions.md
When working on the EleSync repository, prefer the EleSync Maintainer custom agent for Python code, docs, tests, packaging, and release workflow changes.
kasukenCopilot instructionskasuken/vscode-copilot-insights/.github/copilot-instructions.md
VS Code extension project guidelines for GitHub Copilot Insights. Covers project shape, code style, VS Code extension rules, build and test, and repository discipline.
freeCodeCampCopilot instructionsfreeCodeCamp/freeCodeCamp/.github/copilot-instructions.md
file1.md | Updated em dash in seed content | ``` **Good example (actionable feedback only):** ``` Line 46: Test will fail - `innerText` returns rendered `—`, not `—`. ``` --- ## Focus Areas 1. **Test Coverage** - Ensuring adequate testing
No other project uses it yet
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
Steady32 mentions in 2 weeks
2 projects use a version of this
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
No other project uses it yet
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
Significant-GravitasReads credentialsCopilot instructionsSignificant-Gravitas/AutoGPT/.github/copilot-instructions.md
bash cd autogpt_platform/backend poetry run serve # Start development server (port 8000) poetry run test # Run all tests (requires ~5 minutes) poetry run pytest path/to/test.py # Run specific test poetry
Steady3 mentions in 2 weeks
No other project uses it yet
DietrichGebertCopilot instructionsDietrichGebert/ponytail/.github/copilot-instructions.md
task and the code it touches. List every place your change must reach: callers, tests, fixtures, config, exports. Check what your change could break for users: data it would destroy
Steady11 mentions in 2 weeks
No other project uses it yet
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
1 project uses a version of this
MicrosoftCopilot instructionsmicrosoft/PowerToys/.github/copilot-instructions.md
PowerToys AI contributor guidance
excalidrawCopilot instructionsexcalidraw/excalidraw/.github/copilot-instructions.md
operations - Implement proper error boundaries in React components - Always log errors with contextual information ## Testing - Always attempt to fix #problems - Always offer to run `yarn test:app` in the project
1 project uses a version of this
electronCopilot instructionselectron/electron/.github/copilot-instructions.md
through errors e start # Run built Electron e start --version # Verify Electron launches e test # Run full test suite e debug # Run in debugger (lldb on macOS, gdb on Linux
No other project uses it yet
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
Steady6 mentions in 2 weeks
No other project uses it yet
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
axiosCopilot instructionsaxios/axios/.github/copilot-instructions.md
shape, architecture boundaries, naming, error handling, interceptor order, the request lifecycle, cancellation, common pitfalls, tests, and security-sensitive code. The rules below are a Copilot-facing subset of the load
No other project uses it yet
denolandCopilot instructionsdenoland/deno/.github/copilot-instructions.md
libs/` — Shared Rust crates (core, resolver, npm, node_resolver, serde_v8, etc.) - `tests/specs/` — Integration tests (spec tests) - `tests/unit/` — Unit tests - `tests/testdata/` — Test fixtures and data files ### Key Files to Understand
No other project uses it yet
pytorchDeletes or force-pushesCopilot instructionspytorch/pytorch/.github/copilot-instructions.md
DEBUG=1` - Debug symbols with `-g -O0` - `USE_CUDA=0` - Skip CUDA compilation - `BUILD_TEST=0` - Skip C++ test binaries - Install `ninja` (`pip install ninja`) for faster builds - Use `ccache
No other project uses it yet
ant-designCopilot instructionsant-design/ant-design/.github/copilot-instructions.md
size control - Support tree shaking - Browser compatibility: Chrome 80+ - Optimize for minimal re-renders ### Testing Requirements - Write comprehensive tests using Jest and React Testing Library - Target 100% test coverage - Place
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.
