FlashDB
armink/FlashDB/.github/copilot-instructions.md
FlashDB code review instructions FlashDB is an ultra-lightweight embedded database for MCUs, written in plain C99 (no C++, no compiler extensions, no C11 atomics). It provides two databases
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.
armink/FlashDB/.github/copilot-instructions.md
FlashDB code review instructions FlashDB is an ultra-lightweight embedded database for MCUs, written in plain C99 (no C++, no compiler extensions, no C11 atomics). It provides two databases
microsoft/DirectXTK/.github/copilot-instructions.md
level feature checks | > `_M_ARM` / `__arm__` is legacy 32-bit ARM which is deprecated. ## Code Review Instructions When reviewing code, focus on the following aspects: - Adherence to coding standards defined
tkem/cachetools/.github/copilot-instructions.md
constraints, boundaries and git workflow) live in [`AGENTS.md`](../AGENTS.md). This file adds only the code review process. ## Code Review - Reviews **amend `.github/copilot-review.md` in place** (header: date, commit, CI status, coverage
habitat-sh/habitat/.github/copilot-instructions.md
tests and integration tests needed 4. **File Review**: Identify files that will be modified (avoiding prohibited files) ### 3. Implementation Phase 1. **Code Implementation**: - Follow Rust best practices and Habitat coding
intel/neural-compressor/.github/copilot-instructions.md
GitHub Copilot Instructions This file configures GitHub Copilot (code suggestions and PR reviews) to follow the coding standards enforced by the project's pre-commit hooks (`.pre-commit-config.yaml`) and tool configuration
nteract/semiotic/.github/copilot-instructions.md
when a review claim depends on browser rendering, interaction, responsive layout, hydration, or accessibility. When an unstable custom lint fails, evaluate the rule as well as the code before recommending
CommunityToolkit/Maui/.github/copilot-instructions.md
Guidelines * Use GitHub Copilot to assist with code completion, documentation, and generating boilerplate code. * Always review and test the code suggested by GitHub Copilot to ensure it meets the project
flexpilot-ai/flexpilot-ide/.github/copilot-instructions.md
Coding Guidelines ## Introduction These are VS Code coding guidelines. Please also review our [Source Code Organisation](https://github.com/microsoft/vscode/wiki/Source-Code-Organization) page. ## Indentation We use tabs, not spaces. ## Naming Conventions * Use PascalCase
open-telemetry/opentelemetry-java-instrumentation/.github/copilot-instructions.md
Instrumentation rules These rules and the applicable `.github/instructions/*.instructions.md` files guide both implementation and code review. Apply a rule only when its stated conditions hold. Keep its exceptions, rationale
bdring/FluidNC/.github/copilot-instructions.md
channels; any can send commands, read responses - Enables multi-client control (web + serial simultaneously) ## Code Review Checklist - **Naming**: Follows CamelCase (classes), snake_case (methods, members with `_`) - **Includes**: Correct quotes (`"local
spiffe/spire/.github/copilot-instructions.md
processes, the SPIRE Server and the SPIRE Agent, plus a plugin system. When reviewing or generating code, weigh the concerns covered below. All of them matter, and more than
laude-institute/terminal-bench/.github/copilot-instructions.md
tests task completion. Be concise and to the point. Use the following criteria to review the task: 1. **Behavior in Task Description**: Check whether all behavior tested in the test
Checkmk/checkmk/.github/copilot-instructions.md
those when suggesting changes. ## AI tooling lives elsewhere Reusable AI workflows for this project (code review, werk authoring, Gerrit/Jenkins/Jira/crash-report helpers, backports, etc.) are maintained as Claude Code plugins
Steady4 mentions in 2 weeks
No other project uses it yet
eventflow/EventFlow/.github/copilot-instructions.md
install -r requirements.txt` followed by `mkdocs serve` when verifying doc updates. ## Coding conventions & review tips - Favor async APIs and accept `CancellationToken` parameters throughout—the core dispatchers expect cooperative cancellation
Azure/azure-sdk-for-java/.github/copilot-instructions.md
NEVER turn off any Checkstyle or SpotBugs rules to resolve linting issues. - Always review your own code for consistency, maintainability, and testability - Always ask how to verify that your changes
ntex-rs/ntex/.github/copilot-instructions.md
Repository instructions These instructions are for working on ntex itself. Guidance for code that *uses* ntex is in `docs/llms.txt`, published at <https://docs.ntex.rs/llms.txt>. ## Layout Cargo workspace. `ntex
Steady5 mentions in 2 weeks
No other project uses it yet
microsoft/CsWin32/.github/copilot-instructions.md
Copilot instructions for this repository ## High level guidance * Review the `CONTRIBUTING.md` file for instructions to build and test the software. * Set the `NBGV_GitEngine` environment variable to `Disabled` before running
No other project uses it yet
microsoft/Microsoft365DSC/.github/copilot-instructions.md
block, pass state through `PostProcessingArgs`. ## Code Formatting & Style These formatting rules are enforced during code review. Agents must apply them to all generated or modified PowerShell code: 1. **No trailing
omry/omegaconf/.github/copilot-instructions.md
Copilot instructions When generating code or reviewing pull requests for this repository, use `CONTRIBUTING.md` as the source of truth for contributor requirements. For pull request reviews, check the changed files
PSAppDeployToolkit/PSAppDeployToolkit/.github/copilot-instructions.md
patterns over custom non-standard lifecycle hooks, especially for IDisposable/disposal implementations, to keep code review and commit ownership clear. - Avoid changes that cause `DialogManager` static initialization when the client/server process
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.