How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
laisoCopilot instructionslaiso/ts-bench/.github/copilot-instructions.md
never `node` or `npm run`.** - **Any new or changed code must include tests. Run `bun test ./src` and confirm all pass.** - Exercism placeholder code is **intentionally broken**; `--test-only` failures
MicrosoftCopilot instructionsmicrosoft/microsoft-performance-toolkit-sdk/.github/copilot-instructions.md
Size:** Medium-sized repository with SDK core, runtime, engine, plugins system, tools, and comprehensive test coverage ## Build and Test Instructions ### Prerequisites - **.NET SDK 8.x** (or compatible version that supports
MicrosoftCopilot instructionsmicrosoft/XBOX-Godot-Sample/.github/copilot-instructions.md
gdext-gdk.md`, and `tools\setup_sample.ps1` are covered by `.github\instructions\godot-gdk.instructions.md`. - `addons\godot_playfab\`, `tests\godot\playfab\`, the PlayFab-facing sample tracks (`sample\tutorial_playfab\` and `sample\tutorial_integrated\`), `docs
MicrosoftCopilot instructionsmicrosoft/AzureTRE/.github/copilot-instructions.md
setup, auth, and management commands ├── devops - DevOps scripts and bootstrapping tools ├── docs - Documentation ├── e2e_tests - pytest-based end-to-end tests ├── api_app - API source code and docs ├── resource_processor
ffrolivaCopilot instructionsffroliva/gflow-cli/.github/copilot-instructions.md
target` for jobs that checkout or execute contributor code. - For behavior changes, expect focused tests and docs/changelog updates. - Keep findings concrete: reference files/lines, explain the user-visible risk, and separate
Google CloudCopilot instructionsGoogleCloudPlatform/race-condition/.github/copilot-instructions.md
Pub/Sub, PostgreSQL | **Key commands:** `make init` (first-time setup), `make start` (run everything), `make test` (all tests), `make lint` (all linters). ## Project Conventions - **Protobuf**: Generated code is committed
MicrosoftCopilot instructionsmicrosoft/AutoSaddler/.github/copilot-instructions.md
help text, config file comments, and doc examples in sync with actual implementations. ## Testing (IMPORTANT) - **Always run the test suite after significant code changes** (`uv run python -m pytest tests
MicrosoftCopilot instructionsmicrosoft/P.808/.github/copilot-instructions.md
name in a prompt. | Agent | Purpose | Example prompts | |-------|---------|-----------------| | `create-study` | Create subjective speech quality tests (ACR, DCR, CCR, P.835, P.804) | "create a study", "run a P.804 test
GitHubCopilot instructionsgithub/codeql-coding-standards/.github/copilot-instructions.md
Code review guidelines for GitHub copilot in this project
Microsoft AzureCopilot instructionsAzure/fleet/.github/copilot-instructions.md
KubeFleet Copilot Instructions ## Build, Test, and Lint Commands ```bash make build # Build all binaries make reviewable # Run all quality checks (fmt, vet, lint, staticcheck, tidy) — required before PRs make lint
MicrosoftCopilot instructionsmicrosoft/sarif-sdk/.github/copilot-instructions.md
with `NEW:` / `BRK:` / `BUG:` / `BUGFIX:`. - Public surface or behavior change only. Internal refactors and test additions belong in the PR, not in `ReleaseHistory.md`. - Mention concrete names — types, members, CLI flags
yennanliuCopilot instructionsyennanliu/InvestSkill/.github/copilot-instructions.md
portfolio — short- vs. long-term treatment, wash-sale window check, qualified-dividend holding-period test, lot selection (specific-ID vs. FIFO), tax-loss-harvesting pairs, account placement, estimated annual
Conceptual-MachinesCopilot instructionsConceptual-Machines/magda-core/.github/copilot-instructions.md
methods, mixed responsibilities) Files under 300 lines, header files with only declarations, and test files should **never** be refactored. ## Project-Specific Context ### Architecture - **DAW Core** (`magda/daw/`): Main application using JUCE
MicrosoftCopilot instructionsmicrosoft/RecursiveExtractor/.github/copilot-instructions.md
Target Frameworks**: .NET Standard 2.0, .NET Standard 2.1, .NET 8.0, .NET 9.0, .NET 10.0 - **Testing Framework**: xUnit (based on project structure) - **Key Dependencies**: SharpCompress, LTRData.DiscUtils, NLog, Glob ## Building and Testing
MicrosoftCopilot instructionsmicrosoft/duroxide/.github/copilot-instructions.md
without explicit user permission.** Always ask before running `git commit` or `git push`. ## ⚠️ CRITICAL: Test Execution **ALWAYS use nextest for running tests.** This is mandatory - nextest provides faster execution
MicrosoftCopilot instructionsmicrosoft/vs-solutionpersistence/.github/copilot-instructions.md
this repository ## High level guidance * Review the `CONTRIBUTING.md` file for instructions to build and test the software. * Run the `.github/Prime-ForCopilot.ps1` script (once) before running any `dotnet` or `msbuild` commands
azrtydxbCopilot instructionsazrtydxb/procoder/.github/copilot-instructions.md
actually complete. Do not game the checkboxes; the controllers ask for evidence. - Run `procoder test` before claiming anything works. NOT run is never green. Where `[test] policy = "block"`, the closes
FerroxLabsCopilot instructionsFerroxLabs/ijfw/copilot/copilot-instructions.md
solution that works. Self-verify before destructive or irreversible actions. Plan before complex tasks. Test-first when possible. At task boundaries: compact with key decisions preserved. After 2 failed corrections
MicrosoftCopilot instructionsmicrosoft/python-environment-tools/.github/copilot-instructions.md
traits and configuration structures - `docs/JSONRPC.md` - Complete API specification with TypeScript interfaces ## Development Workflow ### Building & Testing ```bash # Standard build cargo build # Release build (optimized for performance) cargo build --release # Run tests
idavidov13Copilot instructionsidavidov13/agentic-playwright/.github/copilot-instructions.md
github/instructions/` and activate automatically when you edit matching files. --- ## Role You are an Automation Test Architect with extensive experience in both API and UI testing using Playwright. Your expertise spans
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.
