How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
Azure-SamplesCopilot instructionsAzure-Samples/snippy/.github/copilot-instructions.md
with `azure.functions.HttpResponse` and **do not** `await` sync methods (`req.get_json()`, `client.create_check_status_response()`). # 👉 Test-generation instructions - Use **pytest** + **pytest-asyncio**. - Mark async tests with `@pytest.mark.asyncio`. - Patch Azure SDK calls
canonicalCopilot instructionscanonical/workshop/.github/copilot-instructions.md
Container Backend**: LXD (primary abstraction target) - **Packaging**: Snap (Snapcraft) - **CLI Framework**: Cobra - **Testing**: Go unit tests (gocheck) + Spread (integration/e2e) - **Documentation**: Sphinx (reStructuredText) - **CI**: GitHub Actions ## Repository Structure ### Core Directories
MicrosoftCopilot instructionsmicrosoft/AntiSSRF/.github/copilot-instructions.md
events (e.g. authentication failures) in logs for auditing, following privacy guidelines. - **Compatible with security testing:** Write code that will pass security static analysis and penetration tests (no high-severity warnings
MicrosoftCopilot instructionsmicrosoft/spec-to-agents/.github/copilot-instructions.md
Framework** for building and orchestrating agents - **uv** for dependency management (NOT pip/poetry/conda) - **pytest** for testing with pytest-mock for mocking - **Microsoft Foundry** for infrastructure (Managed Identity, no API keys) ## Project
ZIZKA-AI-SLCopilot instructionsZIZKA-AI-SL/ZizkaDB/.github/copilot-instructions.md
repo folder mapping 4. [.cursor/rules/coding-standards.mdc](../.cursor/rules/coding-standards.mdc) — ZizkaDB invariants 5. [CLAUDE.md](../CLAUDE.md) — stack map Run tests before claiming done. OSS: no `/v1/admin` routes
natnewCopilot instructionsnatnew/Awesome-Prompt-Engineering/.github/copilot-instructions.md
treat the repository - Treat every change as a documentation edit. There is no build, test, or runtime behaviour to reason about beyond Markdown rendering. - Make the smallest change that achieves
Prism-ShadowCopilot instructionsPrism-Shadow/agenthub/.github/copilot-instructions.md
Python implementation - `agenthub/` - Main Python package - `pyproject.toml` - Python project configuration - `Makefile` - Python build and test commands - `tests/` - Python test files - `src_ts/` - TypeScript implementation - `src/` - TypeScript source files - `package.json` - Node.js
Microsoft AzureCopilot instructionsAzure/LogicAppsUX/.github/copilot-instructions.md
file whose triggers match the task domain (git/worktree, e2e, CI, reviews, customer repro, unit tests, etc.). - For non-trivial work also follow the chief-engineer charter's subagent workflow
growerpCopilot instructionsgrowerp/growerp/.github/copilot-instructions.md
dependencies melos l10n # generate localizations for all packages melos watch # continuous build_runner watch ``` **Testing**: - **Local**: `melos test` (runs integration tests in dependency order) - **Headless CI**: `cd flutter && ./build_run_all_tests.sh` (Docker
MicrosoftCopilot instructionsmicrosoft/Agent365-Samples/.github/copilot-instructions.md
flag for manual review - **Missing header**: Automatically suggest adding the copyright header ### Exclusions - Test files in `Tests/`, `test/`, `tests/`, or files ending with `.Tests.cs`, `.Test.cs`, `_test.py`, `test_*.py`, `.test.js`, `.spec.js
MicrosoftCopilot instructionsmicrosoft/PromptKit/.github/copilot-instructions.md
python tests/validate-instruction-fidelity.py ``` Triggered on push/PR when `manifest.yaml`, component files, or the validation scripts change. ## Testing There is no automated test suite. Testing uses **reference comparison**: hand-crafted known-good prompts
javiarmestoCopilot instructionsjaviarmesto/ALDC-AL-Development-Collection/.github/copilot-instructions.md
user confirmation before proceeding. - **TDD / spec-driven** — Features follow the flow: `architecture (MEDIUM/HIGH) → spec.create → test-plan → implementation → review`. - **Least privilege** — Generate only the minimum permissions required. Use XLIFF
javiarmestoCopilot instructionsjaviarmesto/ALDC-AL-Development-Collection/instructions/copilot-instructions.md
user confirmation before proceeding. - **TDD / spec-driven** — Features follow the flow: `architecture (MEDIUM/HIGH) → spec.create → test-plan → implementation → review`. - **Least privilege** — Generate only the minimum permissions required. Use XLIFF
MicrosoftCopilot instructionsmicrosoft/vscode-powerquery/.github/copilot-instructions.md
Copilot Instructions ## Build, Test, and Lint This is a multi-package monorepo (root, `client/`, `server/`, `scripts/`). Each has its own `node_modules` and `package.json`. The root `npm install` runs
MicrosoftCopilot instructionsmicrosoft/vscode-isort/.github/copilot-instructions.md
isort directly via `script_runner.py`, providing code actions and diagnostics without the LSP server. ## Build & Test Commands ### TypeScript (extension client) ```bash npm run compile # Webpack build (development) npm run package # Webpack
harnessCopilot instructionsharness/harness-skills/.github/copilot-instructions.md
Delete a resource (requires confirmation) | | `harness_execute` | Run, retry, interrupt, sync, toggle, approve, reject, test_connection | | `harness_search` | Cross-resource keyword search | | `harness_describe` | Local metadata/schema lookup (no API call
MicrosoftCopilot instructionsmicrosoft/kanagawa/.github/copilot-instructions.md
/doc/mapping-to-hardware.md) as the authorities for language semantics; do not infer semantics from a single test or implementation detail. - Follow [BUILDING.md](../BUILDING.md) for dependencies, out-of-tree CMake/Ninja builds, and test
nebrassCopilot instructionsnebrass/hve-video-director/.github/copilot-instructions.md
Python helper scripts. There is no build system or lint config; pure-stdlib helper tests live under `test/`. The skill is consumed by future agent sessions that invoke `/hve-video-director
csmar432Copilot instructionscsmar432/finai-research/.github/copilot-instructions.md
scripts/register_mcp_servers.py --profile academic ``` --- ## 约束 - **禁止编造数据** — 始终使用 MCP 工具或用户提供的数据文件 - **引用必须标注来源和日期** - 中文顶刊遵循各自的 LaTeX 模板 - 运行 `pytest tests/` 验证改动
gviiisenCopilot instructionsgviiisen/repo-context-ledger/.github/copilot-instructions.md
unresolved question, and always expand whenever callers, implementations, configuration, persistence, permissions, concurrency, retries, tests, or external boundaries can affect the behavior. A same-window 'continue' on a known active task
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.
