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.
TransformerLensOrgCopilot instructionsTransformerLensOrg/TransformerLens/.github/copilot-instructions.md
main` are maintainer-only. ## Common commands ```bash uv sync # install make unit-test # fast tests make format # pycln + isort + black uv run mypy . # type check uv run docs-hot-reload
kumahqCopilot instructionskumahq/kuma/.github/copilot-instructions.md
sync (Kuma Discovery Service) plugins/policies/ # 20+ policies (api/, plugin/, xds/) config/api-server/dp-server/ # Config, APIs, servers test/ # Test utilities, matchers, builders /test/ # E2E and integration tests /docs/madr/ # Architecture Decision Records ``` **Key Modules
ravendbCopilot instructionsravendb/ravendb/.github/copilot-instructions.md
GitHub Copilot Instructions Repository conventions and architecture: [AGENTS.md](../AGENTS.md). Test authoring and categorization: [test/AGENTS.md](../test/AGENTS.md). Apply both when reviewing or generating code. ## Review emphasis The general review is trusted; additionally
No other project uses it yet
rejettoCopilot instructionsrejetto/hfs/.github/copilot-instructions.md
runs `npm run start --workspace=admin`). - Frontend: `npm run start-frontend`. - Build everything (packaging + tests): `npm run build-all` — this runs audits, compiles server, runs tests, and builds frontends/admin. - Build
corazawafCopilot instructionscorazawaf/coraza/.github/copilot-instructions.md
coding agents lives in [AGENTS.md](../AGENTS.md) at the repository root: architecture and navigation, testing policy and coverage expectations, Architecture Decision Records, pull request requirements and the security policy. Read
spotbugsCopilot instructionsspotbugs/spotbugs/.github/copilot-instructions.md
plugins. Most behavior changes are in `spotbugs/` and usually require matching updates in `spotbugs-tests/`. ## Build and test Primary tool: Gradle wrapper. - Use `./gradlew` from repo root; do not rely
Steady4 mentions in 2 weeks
No other project uses it yet
primerCopilot instructionsprimer/react/.github/copilot-instructions.md
distributes React components for the design system. **Key Directory Structure:** - `e2e/`: End-to-end tests running Visual Regression Tests (@vrt) and Accessibility Verification Tests (@avt) using Playwright - `examples/`: Example applications
No other project uses it yet
pimcoreCopilot instructionspimcore/pimcore/.github/copilot-instructions.md
composer.json should not contain any changes compared to the base branch ## Development Commands ### Testing - **Run all tests**: `vendor/bin/codecept run` - **Run specific test suite**: - Unit tests: `vendor/bin/codecept run Unit` - Service tests
SchemaStoreCopilot instructionsSchemaStore/schemastore/.github/copilot-instructions.md
servers to provide autocompletion and validation. ## Repository Structure - `src/schemas/json/` - JSON Schema files - `src/test/` - Positive test files (JSON, YAML, TOML) - `src/negative_test/` - Negative test files - `src/api/json/catalog.json` - Schema catalog mapping schemas to file
pyvistaCopilot instructionspyvista/pyvista/.github/copilot-instructions.md
file is sometimes all that is loaded: - Run the local gates (`make lint`, `make test-core` or `make test-plotting`, `make doctest`) before pushing. Every push to an open pull
seanmorley15Reads credentialsCopilot instructionsseanmorley15/AdventureLog/.github/copilot-instructions.md
minutes. Subsequent starts: <1 second** - Wait 30+ seconds for services to fully initialize before testing functionality ### Development Workflow Commands **Frontend (SvelteKit with Node.js):** - `cd frontend && npm install` - **45+ seconds, NEVER
neomuttCopilot instructionsneomutt/neomutt/.github/copilot-instructions.md
struct to hold parsed data - Return early on parse errors with clear messages - Write tests for parser BEFORE implementation ### Buffer Pool ✅ ALWAYS release buffers on ALL code paths: ```c struct
MicrosoftCopilot instructionsmicrosoft/mcp/.github/copilot-instructions.md
YAML files (e.g., files in `eng/pipelines/` with `.yml` extension) ## Pull Request Guidelines - Ensure all tests pass - Follow the [contribution guidelines](https://github.com/microsoft/mcp/blob/main/CONTRIBUTING.md) - Include appropriate documentation - Include tests that cover
bytebaseCopilot instructionsbytebase/dbhub/.github/copilot-instructions.md
email) VALUES ('John', 'john@example.com');` - `UPDATE users SET status = 'active' WHERE id = 1;` - `CREATE TABLE test_table (id INT PRIMARY KEY);` Use `--readonly` flag to restrict to read-only operations
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/kiota/.github/copilot-instructions.md
style, naming, and public behavior unless the task requires changes. 3. Add or update tests for behavior changes or bug fixes. 4. Before proposing a commit, run relevant tests
domoticzCopilot instructionsdomoticz/domoticz/.github/copilot-instructions.md
uses 3.31.3) - **Scripting:** Python (plugins and event scripts), Lua (dzVents) - **Frontend:** HTML5, JavaScript - **Testing:** pytest-3 (Gherkin/BDD), mocha (JavaScript), busted (Lua) - **Dependencies:** Boost (>=1.69.0, CI uses 1.86.0), OpenSSL, libcurl, SQLite
KuddevCopilot instructionsKuddev/nebula/.github/copilot-instructions.md
Copilot scope: bug reproduction and regression testing Copilot is used for testing reported bugs, not automatic pull-request review. Work only on the Issue or test task explicitly assigned
pwa-builderCopilot instructionspwa-builder/PWABuilder/.github/copilot-instructions.md
Guidelines for building C# and TypeScript applications
dathereCopilot instructionsdathere/qsv/.github/copilot-instructions.md
project, including API specifications and user guides. - `/resources`: Contains examples, vendored code, and test files used by some tests. - `/scripts`: Contains shell scripts, benchmark tooling, sample data files, Luau scripts
Steady7 mentions in 2 weeks
No other project uses it yet
mckinseyCopilot instructionsmckinsey/vizro/.github/copilot-instructions.md
approval in advance of the PR's submission. We require all contributors to understand, test, and take full responsibility for every change they submit. Pull requests containing AI-generated content
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.
