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.
docmirrorCopilot instructionsdocmirror/dev-sidecar/.github/copilot-instructions.md
manually fix the files indicated by the linter, then re-run the command. - Testing: - Run package tests where they live: - `pnpm --filter @blue-frontier/dev-sidecar test` - `pnpm --filter @blue-frontier
No other project uses it yet
plotlyCopilot instructionsplotly/dash/.github/copilot-instructions.md
with this repository. For detailed documentation, see the [`.ai/`](../.ai/) directory: - [Commands](../.ai/COMMANDS.md) - Build, test, lint - [Architecture](../.ai/ARCHITECTURE.md) - Backend, layout, callbacks - [Components](../.ai/COMPONENTS.md) - Component system, generation, resources ## Project Overview Dash
No other project uses it yet
temporalioCopilot instructionstemporalio/temporal/.github/copilot-instructions.md
acceptable. Report the gap if its consequence matters once the change is released. - A test that asserts a behavior shows that the author intended the behavior, not that the behavior
No other project uses it yet
marimo-teamCopilot instructionsmarimo-team/marimo/.github/copilot-instructions.md
mode, app-view and edit-view? For a backend change, has the user tested different scenarios
No other project uses it yet
pubkeyCopilot instructionspubkey/rxdb/.github/copilot-instructions.md
first, NoSQL) - **Language**: TypeScript - **State Management**: Reactive (RxJS Observables) - **Paths**: Source code in `src/`, tests in `test/`, documentation in `docs-src/`. ## Code Style & Patterns - **Formatting**: Uses ESLint
No other project uses it yet
oxc-projectCopilot instructionsoxc-project/oxc/.github/copilot-instructions.md
them when supported by actual compiler diagnostics. - Treat files inside any `fixtures` directories as test data, not production code. - Fixture files may intentionally contain buggy, unsafe, or syntactically invalid code
No other project uses it yet
dotnetCopilot instructionsdotnet/maui/.github/copilot-instructions.md
Guidance for GitHub Copilot when working on the .NET MAUI repository.
No other project uses it yet
comet-mlCopilot instructionscomet-ml/opik/.github/copilot-instructions.md
Python applications - **TypeScript SDK**: Client library for TypeScript/JavaScript applications - **Documentation**: Comprehensive documentation site - **Testing**: End-to-end and load testing suites ## 1. Git Workflow & Branch Management ### Branch Naming Convention ``` {username
Steady6 mentions in 2 weeks
No other project uses it yet
ratatuiCopilot instructionsratatui/ratatui/.github/copilot-instructions.md
versioning policy**: Point to the requirement of at least one version notice before removal ### Testing and Documentation - **Verify test coverage**: Ensure new functionality includes appropriate tests - **Check for test removal
No other project uses it yet
mochajsCopilot instructionsmochajs/mocha/.github/copilot-instructions.md
safe. 3. Never edit generated bundle artifacts (`mocha.js`, `mocha.js.map`) directly. 4. Validate with targeted tests first, then broader checks as needed. 5. Prefer repository `npm` scripts and workflow-defined commands
No other project uses it yet
foremCopilot instructionsforem/forem/.github/copilot-instructions.md
major subsystem, explicitly ask clarifying questions to validate isolation and proactively determine if extra tests are needed to guarantee no side-effects occur. ## Background Workers & Sidekiq - **Job Storm Prevention**: When
No other project uses it yet
desktopCopilot instructionsdesktop/desktop/.github/copilot-instructions.md
Node.js version in `.nvmrc`) - **Node Version**: >= 22.12.0 (see `.nvmrc` for the recommended version) - **Testing**: Node.js built-in test runner (run using `npm test`, optionally providing one or more test files
No other project uses it yet
dotnetCopilot instructionsdotnet/core/.github/copilot-instructions.md
Validation Commands Always run these validation commands before committing changes. All commands have been tested and work correctly: 1. **Markdown linting** (takes ~1 second): ```bash npx markdownlint --config .github/linters/.markdown-lint.yml
No other project uses it yet
gitbutlerappDeletes or force-pushesCopilot instructionsgitbutlerapp/gitbutler/.github/copilot-instructions.md
comment injector package The `e2e` directory contains Playwright, WebdriverIO, and blackbox end-to-end tests. ## Technology Stack - **Frontend**: Svelte with TypeScript - **Backend**: Rust - **Desktop Framework**: Tauri (like Electron but using
No other project uses it yet
onnxCopilot instructionsonnx/onnx/.github/copilot-instructions.md
project-wide requirement for human contributors: ``` ( ): ``` - `type`: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore`, or `revert` - `scope`: optional, e.g. the affected area (`defs`, `shape_inference`, `ci`, `docs
No other project uses it yet
CaldisCopilot instructionsCaldis/Mos/.github/copilot-instructions.md
NSLocalizedString(_:comment:)` and the two separate `.xcstrings` catalogs. - `Mos/Logi` / `Mos/Integration` boundaries and `scripts/qa/lint-logi-boundary.sh`. - Regression tests for bug fixes and clear verification evidence before claiming success. - Human confirmation before release, signing
No other project uses it yet
wasmerioCopilot instructionswasmerio/wasmer/.github/copilot-instructions.md
changes - Run the commands for formatting - Run the linter command shown below - Run tests for code you changed and everything that depends on it. - CI will reject code with formatting
No other project uses it yet
monkeytypegameCopilot instructionsmonkeytypegame/monkeytype/.github/copilot-instructions.md
suffixes for targeted execution: ```bash pnpm run lint-fe # Frontend linting pnpm run test-be # Backend + integration tests pnpm run build-pkg # Packages only pnpm run dev # All workspaces with
No other project uses it yet
dotnetCopilot instructionsdotnet/roslyn/.github/copilot-instructions.md
RoslynAnalyzers/ eng/ # Arcade build engineering (eng/common is DARC-synced) docs/ # Contributor & design docs ``` ## Build & Test ### Build specific projects during development (preferred) ```bash dotnet build Compilers.slnf # compilers only dotnet build Ide.slnf
No other project uses it yet
realmCopilot instructionsrealm/SwiftLint/.github/copilot-instructions.md
removed to (un-)register them from/in the list of built-in rules and tests verifying all examples in rule descriptions. For some rules, there are dedicated tests in `Tests/BuiltInRulesTests`. However
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.
