How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
AMD-AGICopilot instructionsAMD-AGI/Hyperloom/.github/copilot-instructions.md
invariants**: a change that silently alters an external contract or breaks a documented rule. - **Test strategy**: exported behaviour — a CLI flag, public function, persisted schema, artifact layout — landing without
MicrosoftCopilot instructionsmicrosoft/azure-devops-extension-tasks/.github/copilot-instructions.md
Manifest adjustments: `fix-manifest-file.ps1` cleans & re-adds certain binary/no-extension files before packaging. - Test scripts (`test-*.cmd`) emulate agent execution by setting `INPUT_*` env vars matching `task.json` inputs
MicrosoftCopilot instructionsmicrosoft/MicroHack/03-Azure/01-04-AI/01_Agentic_SDLC/.github/copilot-instructions.md
NotFound, Validation, Conflict) and propagates consistent HTTP status codes via middleware. 6. Encourage tests: request unit tests for new repository logic and component tests (or at least React Testing Library
MicrosoftCopilot instructionsmicrosoft/vscode-java-dependency/.github/copilot-instructions.md
Copilot instructions for vscode-java-dependency ## UI and E2E tests - When asked to add, update, run, or debug UI/E2E coverage, prefer the AutoTest YAML workflow under `test/e2e-plans/`. - Use the `uitest
KbWenCopilot instructionsKbWen/agentic-os/.github/copilot-instructions.md
review priorities. - Prefer focused, file/line-specific findings over broad style suggestions. - Treat correctness, security, missing tests, governance-bypass, and stale spec/backlog/SSoT metadata as higher priority than formatting. - Do not duplicate
thomast1906Copilot instructionsthomast1906/github-copilot-agent-skills/.github/copilot-instructions.md
deployment - Active-passive or active-active configurations - Geo-replication for data - Defined RTO/RPO and tested DR procedures ## Cost Optimization Guidelines **Design phase:** - Right-size based on actual requirements, not "just
MicrosoftCopilot instructionsmicrosoft/vscode-black-formatter/.github/copilot-instructions.md
Copilot Instructions for vscode-black-formatter ## Development Guidelines - When introducing new functionality, add basic tests following the existing repo test structure. - Always make sure all tests pass before submitting changes
MicrosoftCopilot instructionsmicrosoft/durabletask-dotnet/.github/copilot-instructions.md
added to the solution file in the samples directory. - The sample should be tested to ensure it works as expected. - A reference to the new sample should be added
CelestoAICopilot instructionsCelestoAI/agentor/.github/copilot-instructions.md
single source of contributor guidance for this project — architecture, development setup, code style, testing, and CI — and applies to Copilot exactly as written. This file used to be a full
SebastienDegodezCopilot instructionsSebastienDegodez/copilot-instructions/.github/copilot-instructions.md
Follow TDD when it is possible. Always start new changes by writing new test cases (or changing existing tests). Remember to consult [Unit and Integration Tests](./instructions/unit-and-integration-tests.instructions.md) for details
sortie-aiCopilot instructionssortie-ai/sortie/.github/copilot-instructions.md
error; never silently succeeds. - Reads of `Manager.currentConfig`/`currentPrompt` hold the appropriate lock. ## 9. Testing - Race detector required; `make test` runs `-race`. - Test error paths and spec edge cases (CRLF
rcarmoCopilot instructionsrcarmo/vibes/.github/copilot-instructions.md
should prefer `pip3 install --user --break-system-packages` over a `venv`. ## Build, lint, and test - Prefer Makefile targets for common workflows (e.g., `make lint`, `make lint-frontend`, `make test`, `make
zhaoliangbin42Copilot instructionszhaoliangbin42/AI-MarkDone/.github/copilot-instructions.md
fill) for consistency - **Placeholder pattern**: Math/code use placeholders during Turndown, then restore (see `MathExtractor.generatePlaceholder()`) ## Testing Scenarios Reference HTML files in root (`ChatGPT-Success.html`, `ChatGPT-Fail.html`, `ChatGPT-DeepResearch.html`) show: - **Success**: Rendered KaTeX with `data
CortexPrismCopilot instructionsCortexPrism/cortex/.github/copilot-instructions.md
recent deploys" → `entity(kind="release", action="list", query={"status": "released"})` - "create experiment" / "start A/B test" → `entity(kind="experiment", action="create", body={"name": "...", "hypothesis": "...", "control": "...", "treatment": "...", "primary_metric": "..."})` - "list experiments" / "running
Microsoft AzureCopilot instructionsAzure/gpt-rag-ingestion/.github/copilot-instructions.md
exact ingestion commit or image with the compatible GPT-RAG umbrella/component versions; - capture test, build, and deployment evidence appropriate to the change; - verify rollback or roll-forward steps; - remove personal
phil65Copilot instructionsphil65/agentpool/.github/copilot-instructions.md
Consider using pattern matching, walrus operators and other new syntax features. Adhere to pep8. ## Tests Tests are written using PyTest. Dont put tests into a class. ## DocStrings DocStrings are written
MicrosoftCopilot instructionsmicrosoft/bocpy/.github/copilot-instructions.md
MPSC message queues | | `src/bocpy/_math.c` | Dense matrix implementation | | `src/bocpy/examples/` | Runnable demos (bank, boids, dining philosophers, …) | | `test/` | pytest test suite | | `sphinx/` | Sphinx documentation source and build | | `setup.py` | C extension build configuration | | `pyproject.toml
adezeCopilot instructionsadeze/raindrop-mcp/.github/instructions/copilot-instructions.md
easy addition of new tools/operations. Use a registry or factory pattern for tool handlers. - **Testing**: Use [Vitest](https://vitest.dev/) for all tests. Place tests in `tests/` and cover protocol
thalysjuvenalCopilot instructionsthalysjuvenal/advpl-specialist/.github/copilot-instructions.md
TDS/VS Code TOTVS extension. For task-specific guidance (code generation, review, debugging, migration, SQL, tests, locks, Smart X, SX dictionary), consult `skills/ /SKILL.md` per the map in `AGENTS.md
cortex-tmsCopilot instructionscortex-tms/cortex-tms/.github/copilot-instructions.md
Tier system (HOT/WARM/COLD) - Examples MUST be real (not theoretical) - Guides MUST be tested on actual projects ## 🔧 Development Protocol 1. **Plan before code** — Every feature starts with a written plan
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.
