Copilot instructions examples

stellarCopilot instructions

stellar-core

stellar/stellar-core/.github/copilot-instructions.md

over a decade). There is a lot of old code and a lot of tests. There is a team of skilled engineers working on it. The code is also live

music-assistantCopilot instructions

server

music-assistant/server/.github/copilot-instructions.md

error. ## What to review Correctness and bugs, blocking IO in async code, security, performance, test coverage, docs the change makes wrong, and consistency with the surrounding code. `AGENTS.md` holds

No other project uses it yet

MicrosoftCopilot instructions

litebox

microsoft/litebox/.github/copilot-instructions.md

Build**: `cargo build` 3. **Lint**: `cargo clippy --all-targets --all-features` 4. **Test**: `cargo nextest run` - Full CI checks are defined in `.github/workflows/ci.yml`. ## Key Guidelines 1. Follow Rust best practices

InvoicePlaneReads credentialsCopilot instructions

InvoicePlane

InvoicePlane/InvoicePlane/.github/copilot-instructions.md

currently contain `—`. Do not alter neighbouring columns (score, CWE, severity) as a side-effect. ## Testing - Tests are written with **PHPUnit** (no Laravel TestCase — use plain PHPUnit). - Test files

No other project uses it yet

FluidInferenceCopilot instructions

FluidAudio

FluidInference/FluidAudio/.github/copilot-instructions.md

FluidAudio - Agent Development Guide ## Build & Test Commands ```bash swift build # Build project swift build -c release # Release build swift test # Run all tests swift test --filter CITests # Run single test

No other project uses it yet

vitodeployCopilot instructions

vito

vitodeploy/vito/.github/copilot-instructions.md

app/Helpers/SSH.php` and the `SSH` facade. Never shell out directly. Use `SSH::fake()` in tests. - **Providers** (server, DNS, storage, source control) follow an Interface + AbstractProvider pattern. New providers extend the abstract

dotnetPipes a download into a shellCopilot instructions

extensions

dotnet/extensions/.github/copilot-instructions.md

abstractions, compliance mechanisms, diagnostics, contextual options, resilience (Polly), telemetry, AspNetCore extensions, static analysis, and testing utilities. ## Working Effectively ### Prerequisites and Bootstrap - **CRITICAL**: Ensure you have access to the appropriate Azure

AvaloniaCommunityCopilot instructions

awesome-avalonia

AvaloniaCommunity/awesome-avalonia/.github/copilot-instructions.md

Videos - Articles - Community - Tooling ## Important Notes - **NO BUILD PROCESS**: This repository has no compilation, testing, or build steps - **NO DEPENDENCIES**: No package.json, requirements.txt, or similar dependency files - **CONTENT FOCUS**: Primary

MicrosoftCopilot instructions

Generative-AI-for-beginners-dotnet

microsoft/Generative-AI-for-beginners-dotnet/.github/copilot-instructions.md

code formatting and style - Ensure all code builds with `dotnet build` and passes tests with `dotnet test` - Verify formatting with `dotnet format --verify-no-changes` if linting is enabled - **Build

SynoCommunityCopilot instructions

spksrc

SynoCommunity/spksrc/.github/copilot-instructions.md

packagename-1.2.3.tar.gz SHA1 abc123... packagename-1.2.3.tar.gz SHA256 def456... packagename-1.2.3.tar.gz MD5 789ghi... ``` Regenerate with: `make digests` ## Validation ### Testing Builds ```bash # Test build for a specific architecture cd spk/packagename make arch-x64-7.2 # Check

subsurfaceCopilot instructions

subsurface

subsurface/subsurface/.github/copilot-instructions.md

othe other `packaging/*` directories, as well as in the `.github/workflows` ### Running Tests - Tests are located in the `tests/` directory. - Use the following command to run tests: ```bash make test ``` --- ## Project

MicrosoftCopilot instructions

skills

microsoft/skills/.github/copilot-instructions.md

requested. - If you write 200 lines and it could be 50, rewrite it. **The test:** Would a senior engineer say this is overcomplicated? If yes, simplify. ### 3. Surgical Changes **Touch

warp-drive-dataCopilot instructions

warp-drive

warp-drive-data/warp-drive/.github/copilot-instructions.md

task is about *using* WarpDrive's public API rather than changing its internals — a test app, a docs example, a guide snippet — the consumer index at `warp-drive-packages/memory-alpha/skills/index.md

GitToolsCopilot instructions

GitVersion

GitTools/GitVersion/.github/copilot-instructions.md

Copilot agent instructions See [AGENTS.md](../AGENTS.md) for repo-specific guidance (architecture, developer commands, conventions, testing patterns, and the release process

MicrosoftCopilot instructions

mxc

microsoft/mxc/.github/copilot-instructions.md

from names. - Follow any matching file-scoped instructions under `.github/instructions/`. - Inspect nearby code and tests before editing. Reuse existing abstractions and error types. - Do not hand-edit generated files

lammpsCopilot instructions

lammps

lammps/lammps/.github/copilot-instructions.md

plus the path-specific rules in `.github/instructions/` for the changed files: C++ sources and tests (`source-code`), documentation (`documentation`), KOKKOS (`kokkos`), unit tests (`force-style-tests`), example inputs (`regression-tests

Open-Cascade-SASCopilot instructions

OCCT

Open-Cascade-SAS/OCCT/.github/copilot-instructions.md

explicit user approval and a separate explanation of the unresolved defect. - Add a regression test that fails for the original reason before the fix and passes afterward. Include nearby boundary

inspecCopilot instructions

inspec

inspec/inspec/.github/copilot-instructions.md

GitHub Copilot Instructions for InSpec ## Project Overview InSpec is an open-source infrastructure testing framework written in Ruby. It provides a domain-specific language (DSL) for describing security and compliance

anandnetCopilot instructions

Harmony-Music

anandnet/Harmony-Music/.github/copilot-instructions.md

Building ```bash # Android flutter build apk # Windows flutter build windows # Linux flutter build linux ``` ### Testing ```bash flutter test ``` ## Coding Guidelines 1. **Follow Dart/Flutter best practices**: - Use `flutter_lints` package rules

pulumiCopilot instructions

kubespy

pulumi/kubespy/.github/copilot-instructions.md

minutes. - **Install the application:** - `make install` -- installs to $GOPATH/bin, takes ~5 seconds. ### Testing - **Run tests:** - `make test_all` -- runs all tests (takes ~13 seconds first time, <1 second subsequent runs