How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
MicrosoftCopilot instructionsmicrosoft/winget-command-not-found/.github/copilot-instructions.md
default in PowerShell 7.5+): ```powershell Enable-ExperimentalFeature PSFeedbackProvider Enable-ExperimentalFeature PSCommandNotFoundSuggestion ``` ## Building, Testing, and Running ### Setup ```powershell .\build.ps1 -Bootstrap ``` ### Building ```powershell .\build.ps1 -Configuration Debug # or -Configuration Release ``` ### Running/Debugging ```powershell Import
ohad6kCopilot instructionsohad6k/VibeRaven/.github/copilot-instructions.md
before launch, deployment, real users, auth, billing, database, RLS, env vars, webhooks, monitoring, or tests. Agent loop: run VibeRaven, read Mission Map (`.viberaven/mission-map.md`), fix one launch gap, re-run VibeRaven
MicrosoftCopilot instructionsmicrosoft/a11y-llm-eval/.github/copilot-instructions.md
schema, pass/fail, caching, report path/format): - Update `docs/features-and-acceptance.md` in the same PR. - Update or add tests in `tests/` to lock the new behavior. - Call out breaking changes and any migration steps
MicrosoftCopilot instructionsmicrosoft/cmd-call-graph/.github/copilot-instructions.md
parsing of CMD/BAT files - **Analyzer**: Builds call relationships and dependencies - **Visualizer**: Generates graph outputs ## Testing Guidelines - Test with various complexity levels of batch files - Include edge cases like recursive calls
MicrosoftCopilot instructionsmicrosoft/fabric-jumpstart/.github/copilot-instructions.md
workflows, issue/PR templates ├── contrib/ # Bootstrap scripts for dev environment setup ├── dev/ # Development and testing notebooks (.ipynb) ├── src/ │ ├── fabric_jumpstart/ # Python library (published to PyPI) │ │ ├── fabric_jumpstart/ # Importable Python package │ │ │ ├── core.py
ebibibiCopilot instructionsebibibi/ebi-agent-chat-relay/.github/copilot-instructions.md
linting and formatting (line-length: 100) - **pytest** with pytest-asyncio (auto mode) for testing - **Never use `shell=True`** in subprocess calls — always `create_subprocess_exec` - **Validate all user input** before
Michael-ObeleCopilot instructionsMichael-Obele/shadcn-svelte-mcp/.github/copilot-instructions.md
Workers. Do not add static `node:*` imports to shared services used by `src/worker.ts`. - **Test file organization**: ALWAYS place test files in the `test/` directory at the repository root, never
MicrosoftCopilot instructionsmicrosoft/wmi/.github/copilot-instructions.md
status checks show a passing status before removing the draft status 3. **All automated tests must pass**: Ensure all test suites complete successfully 4. **Code quality checks must pass
spboyerCopilot instructionsspboyer/sensei/.github/copilot-instructions.md
checks after changes: ```bash npm run tokens -- check [paths...] npm run tokens -- score . npm test ``` Use `npm run tokens -- count [paths...]`, `npm run tokens -- suggest [paths...]`, or `npm run tokens
MicrosoftCopilot instructionsmicrosoft/BC-Bench/.github/copilot-instructions.md
designed to grow over time. It currently has two categories, `bug-fix` and `test-generation`. They share the same dataset tasks and execution-based setup, but use different prompts, expected
zircoteCopilot instructionszircote/rlm-rs/.github/copilot-instructions.md
edition) - **Build System**: Cargo - **Linting**: clippy with pedantic and nursery lints - **Formatting**: rustfmt - **Testing**: Built-in test framework + proptest - **Supply Chain Security**: cargo-deny ## Code Generation Guidelines ### Error Handling
AzureCosmosDBCopilot instructionsAzureCosmosDB/cosmosdb-agent-kit/.github/copilot-instructions.md
contains AI coding agent skills (best practice rules) for Azure Cosmos DB, plus a testing framework that measures how well agents apply those skills when building apps. ## Key Directories - `skills/cosmosdb-best-practices
dotnet-presentationsCopilot instructionsdotnet-presentations/ai-workshop/.github/copilot-instructions.md
github/instructions/` for workshop prose, snapshot code, and the shared GenAiLab progression. - Use the `workshop-testing` skill for attendee-style walkthroughs, snapshot reconciliation, or workshop test reports. - Consult `docs/instructor/` for volatile
jango-blockchainedCopilot instructionsjango-blockchained/advanced-homeassistant-mcp/.github/copilot-instructions.md
bash npm run start ``` - **Run the STDIO-only server**: ```bash npm run start:stdio ``` ### Testing - **Run all tests**: ```bash bun test ``` *Note: The test runner is still `bun test` even
0xmariowuCopilot instructions0xmariowu/AgentLint/.github/copilot-instructions.md
this repo must follow the rules below. ## Hard rules — never violate 1. **No test assertion mutation.** If a test is failing, fix the code or file a bug — never change
Microsoft AzureCopilot instructionsAzure/azure-kusto-node/.github/copilot-instructions.md
Copilot Instructions for azure-kusto-node ## Build, Test, and Lint This is an npm workspaces + Lerna monorepo with two packages: `azure-kusto-data` and `azure-kusto-ingest`. ```bash
MicrosoftCopilot instructionsmicrosoft/CoseSignTool/.github/copilot-instructions.md
tags appropriately - Where possible provide appropriate ` ` tags for different behaviors - Document exceptions with ` ` tags ### Testing Patterns - Use descriptive test method names - Follow Arrange-Act-Assert pattern - Use meaningful assertions with
MicrosoftCopilot instructionsmicrosoft/LakeBench/.github/copilot-instructions.md
benchmark`, `benchmark_version`, `mode`, `scale_factor`, `scenario`, `total_cores`, `compute_size`, `phase`, `sub_phase`, `test_item`, `start_datetime`, `duration_ms`, `estimated_retail_job_cost`, `iteration`, `success`, `error_message`, `sql_text
MicrosoftCopilot instructionsmicrosoft/mssql-rs/.github/copilot-instructions.md
mssql-tds-cli` | Interactive CLI client | 2024 | | `mssql-mock-tds` | Mock TDS server for testing | 2024 | | `mssql-py-core` | Python bindings (PyO3/maturin) — **excluded from workspace** | 2021 | | `mssql-odbc` | ODBC driver
naviktCopilot instructionsnavikt/copilot/.github/copilot-instructions.md
system at the end **Six Core Areas to Cover:** - Commands (with flags and options) - Testing patterns - Project structure - Code style (✅ Good / ❌ Bad examples) - Git workflow - Boundaries **Three-Tier Boundaries:** ```markdown
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.
