How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
andreaswasitaCopilot instructionsandreaswasita/copilot-agents-dojo/.github/copilot-instructions.md
strict: true` - Naming: camelCase for variables/functions, PascalCase for components/types - Styling: Tailwind CSS + shadcn/ui components - Testing: Write Vitest tests for every new component/logic - Architecture: Next.js App Router, Server Actions, React Server
Microsoft AzureCopilot instructionsAzure/azure-openapi-validator/.github/copilot-instructions.md
Ruleset implementations (`@microsoft.azure/openapi-validator-rulesets`) - `src/spectral/` - Spectral format rules - `src/native/` - Native TypeScript rules - `regression` - Regression tests ## Build and Test Commands ### Prerequisites - Node.js >= 18.0.0 (some packages like rulesets require >= 20) - Rush.js
call518Copilot instructionscall518/MCP-Airflow-API/.github/copilot-instructions.md
interface (port 3002) **Build Commands:** Use versioned Docker images: ```bash ./build-mcp-server-docker-image.sh # Builds call518/mcp-server-airflow-api:1.0.0 ``` ## Testing Philosophy Tests in `tests/test_prompt_template.py` are "resilient to template content changes": - Use `TEMPLATE_CONFIG` constants
GitHubCopilot instructionsgithub/octocanvas/.vscode/.github/copilot-instructions.md
deploys to GitHub Pages (production) - **Prototype Branch**: Builds but doesn't auto-deploy (safe testing) - **Manual Deploy**: Can deploy any branch via workflow_dispatch - **Base Path**: `/octocanvas` ### Configuration ```javascript // astro.config.mjs
MicrosoftCopilot instructionsmicrosoft/Trieste/.github/copilot-instructions.md
declarative specifications of valid AST shapes, used for validation and automatic fuzz-test generation. Language implementation in Trieste is a pipeline: `Parse → Pass₁ → Pass₂ → ... → Passₙ → Output`, where each pass rewrites
nubbymongCopilot instructionsnubbymong/claude-command-center/.github/copilot-instructions.md
WebGL addon, node-pty for PTY management - **Build**: electron-vite, electron-builder for packaging - **Testing**: Vitest (unit), Playwright (E2E) - **Color palette**: Catppuccin Mocha - use theme tokens (base, mantle, crust, surface0
WYRE-AICopilot instructionsWYRE-AI/autotask-mcp/.github/copilot-instructions.md
Actions — CI on push, semantic-release on main, Docker build + MCPB upload on release - **Testing**: Jest with `ts-jest` ## Priority Areas (Review These) ### Security - Credentials must NEVER be logged, even
Microsoft AzureCopilot instructionsAzure/kafka-sink-azure-kusto/.github/copilot-instructions.md
state, any `pom.xml` change, any new HTTP/network code. - **Medium** — touches config, writers, format dispatch, tests of hot paths, retries, logging on hot paths. - **Low** — docs, comments, README, unit tests
FmarzochiCopilot instructionsFmarzochi/EGC/.github/copilot-instructions.md
processes (~/.egc state, encryption key, install-state, lockfiles) requires a concurrent-access regression test; check for read-merge-write races and lock steal in upserts. - Shell-facing features must
MicrosoftCopilot instructionsmicrosoft/moc/.github/copilot-instructions.md
build jobs must complete without errors: - `Build` job (includes protobuf generation, compilation, and unit tests) - `Lint` job (GolangCI-Lint must pass) - ✅ GitHub Actions workflows must complete successfully: - CodeQL analysis must
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.
