How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
MicrosoftCopilot instructionsmicrosoft/WindowsProtocolTestSuites/.github/copilot-instructions.md
base types | | **TransportStack** | Network transport implementations (TCP, UDP, named pipes, RDP virtual channels) | | **Sspi/SspiLib** | Security Support Provider Interface (NTLM, Kerberos, Negotiate authentication) | | **CryptoLib** | Cryptographic operations (AES-CCM, AES-GCM, encryption/decryption
vltpkgCopilot instructionsvltpkg/vltpkg/.github/copilot-instructions.md
src/init - `@vltpkg/init` - Implements the logic for the `vlt init` command - src/keychain - `@vltpkg/keychain` - Implements a secure way to store authorizaton tokens to access registries - src/output, `@vltpkg/output` - CLI output formatting - src/package-info, `@vltpkg/package-info
OpenDevicePartnershipCopilot instructionsOpenDevicePartnership/patina/.github/copilot-instructions.md
applicable. ## Dependency Management - All external dependencies are vetted via `cargo-deny` for license compatibility, security advisories, and allowed sources. - Use workspace-level dependency declarations in the root `Cargo.toml` for consistency
Microsoft AzureCopilot instructionsAzure/karpenter-provider-azure/.github/copilot-instructions.md
short form; `AGENTS.md` is the source of truth. ## Priorities Review for correctness, security, and backward compatibility, in that order. Focus on architecture, logic bugs, and failure modes. Reason about
celestiaorgCopilot instructionscelestiaorg/celestia-core/.github/copilot-instructions.md
implicit operation must be called out. 3. Follow instructions exactly. Think critically about security: always double-check for hidden bugs or vulnerabilities. 4. Produce readable yet concise code without premature
40rbidd3nReads credentialsCopilot instructions40rbidd3n/Hydro0x01/.github/copilot-instructions.md
sensor tags are extracted via topic parsing (see `mqtt.service.ts` lines 47–87). ### 2. Validation & Security Model - **Environment variables**: All required env vars validated via Zod at startup in `config/env.ts` → kills
MicrosoftCopilot instructionsmicrosoft/pxt-arcade/.github/copilot-instructions.md
Firefox, Safari, Edge) - Mobile device compatibility - Hardware device compatibility - Backward compatibility with existing projects ### Security Guidelines: - Follow Microsoft security policies - Validate user-generated content - Secure handling of shared projects - Privacy
clawdotnetCopilot instructionsclawdotnet/openclaw.net/.github/copilot-instructions.md
where possible. ## Architecture priorities - Core runtime should remain lightweight. - Optional integrations must stay optional. - Security and hardening take precedence over convenience for public-bind scenarios. - New tool execution paths should
proffesor-for-testingCopilot instructionsproffesor-for-testing/agentic-qe/.github/copilot-instructions.md
Assessment - `quality_assess` — Quality gate evaluation with configurable thresholds - Run before marking tasks complete ### Security Scanning - `security_scan_comprehensive` — SAST/DAST vulnerability scanning - Run after changes to auth, security, or middleware
web3infra-foundationCopilot instructionsweb3infra-foundation/mega/.github/copilot-instructions.md
secrets. - Provide actionable error messages (context via anyhow::Context), and map OS/IO errors precisely. ## Security & compliance - No plaintext secrets, keys, or tokens in code or tests. - Default to Rustls
labbotsCopilot instructionslabbots/NiimPrintX/.github/copilot-instructions.md
info) flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics ``` ### Security Scanning Use CodeQL for security analysis: ```bash # CodeQL analysis is configured in GitHub Actions # Check .github/workflows/python-app.yml
zaxbysauceCopilot instructionszaxbysauce/opencode-swarm/.github/copilot-instructions.md
Standards These standards apply to all Copilot interactions including code generation and PR review. ## Security - Never hardcode secrets, tokens, API keys, or connection strings — use environment variables or a vault
MicrosoftCopilot instructionsmicrosoft/AL-Go/.github/copilot-instructions.md
modules with explicit paths: `Join-Path $PSScriptRoot` pattern. - Use `-Force -DisableNameChecking` for re-imports. ## Security Patterns ### Secret Handling - Mask secrets with `Write-Host "::add-mask::$secret"` before any output. - Never
schollzCopilot instructionsschollz/e2ecp/.github/copilot-instructions.md
e2ecp - Copilot Agent Instructions ## Repository Overview **e2ecp** is a secure, end-to-end encrypted file transfer application that enables peer-to-peer file sharing through a web interface or command
OfficeDevReads credentialsCopilot instructionsOfficeDev/microsoft-365-agents-toolkit-samples/ProxyAgent-Python/copilot-instructions.md
Oryx build (SCM_DO_BUILD_DURING_DEPLOYMENT=true) - Async context managers for resource management ## Security Best Practices - Never commit secrets or `.env` files - Use Managed Identity in production (no secrets
1c-syntaxCopilot instructions1c-syntax/bsl-language-server/.github/copilot-instructions.md
qa.yml` - Runs tests and code quality checks - **Pre-QA:** `pre-qa.yml` - Quick validation - **CodeQL:** `codeql-analysis.yml` - Security analysis - **Releases:** `release.yml` - Automated release process Always ensure your changes pass all CI checks before
canonicalCopilot instructionscanonical/lxd-ui/.github/copilot-instructions.md
complex logic - E2E tests with Playwright for user workflows - Use test helpers from `tests/helpers/` ### Security - No hardcoded secrets or API keys - Validate user inputs before API calls - Sanitize rendered HTML
roostorgCopilot instructionsroostorg/osprey/.github/copilot-instructions.md
SQLAlchemy for persistence (versions pinned in `pyproject.toml`). ## Scope of review — focus on quality and security Lint and formatting are enforced in CI, so please skip: - formatting, whitespace, indentation, quote style
MicrosoftCopilot instructionsmicrosoft/xdp-for-windows/.github/copilot-instructions.md
ring perf, RX filter perf 5. **Fuzz Tests**: Packet parsing fuzzer (pktfuzz) 6. **CodeQL**: Security analysis (on scheduled runs) CI uses test-signed drivers and requires test signing enabled
PolprzewodnikowyCopilot instructionsPolprzewodnikowy/N64FlashcartMenu/.github/copilot-instructions.md
warnings unless repeated usage already exists. - Local constants are allowed when they encode validation, security, or out-of-bounds safety limits (including one-off scan-limit values). - Keep behavior identical
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.
