How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
MicrosoftCopilot instructionsmicrosoft/pyright/.github/copilot-instructions.md
unreachableCode, deprecated)`. - Sample `.py` files use comments like `# This should generate an error` to document expected diagnostics, but the actual assertion is the count passed to `validateResults`. **Fourslash tests** (`src/tests/fourslash
open-metadataCopilot instructionsopen-metadata/OpenMetadata/.github/copilot-instructions.md
established best practices and conventions - Include error handling and edge case considerations - Provide clear documentation and usage examples - Explain technical decisions and trade-offs - Test solutions mentally before presenting them
MicrosoftCopilot instructionsmicrosoft/agent-framework/.github/copilot-instructions.md
Python implementation → see [python/AGENTS.md](../python/AGENTS.md) - `dotnet/` - C#/.NET implementation → see [dotnet/AGENTS.md](../dotnet/AGENTS.md) - `docs/` - Design documents and architectural decision records ## Architectural Decision Records (ADRs) ADRs in `docs/decisions/` capture significant design decisions
InsForgeCopilot instructionsInsForge/InsForge/.github/copilot-instructions.md
/functions`: Serverless function runtime - `/shared-schemas`: Shared TypeScript schemas - `/docker-init`: Docker initialization scripts - `/openapi`: API documentation in OpenAPI format - `/tests`: Comprehensive test suites ## Libraries and Frameworks ### Backend - Express.js for REST
MicrosoftCopilot instructionsmicrosoft/windows-rs/.github/copilot-instructions.md
test_reactor`, integration tests in `test-reactor-selftest`. Canvas tests use WARP software rendering. ## Documentation The `docs/` folder has one page per crate: - **`docs/crates/ .md`** - a single page per crate
MicrosoftCopilot instructionsmicrosoft/garnet/.github/copilot-instructions.md
Object command tests go in `test/Garnet.test/Resp[ObjectName]Tests.cs`, others in `test/Garnet.test/RespTests.cs` or similar. 9. **Documentation**: Update the appropriate markdown file under `website/docs/commands/` and mark the command as supported in `website/docs/commands/api-compatibility.md
HashiCorpCopilot instructionshashicorp/terraform-provider-aws/.github/copilot-instructions.md
instructions/acceptance-tests.instructions.md` | `internal/service/**/*_test.go` | | Test helpers (Exists/Destroy, list/data source/unit tests) | `instructions/acceptance-tests-helpers.instructions.md` | `internal/service/**/*_test.go` | | User-facing documentation | `instructions/docs.instructions.md` | `website/docs/**/*.markdown` | | Import section + Identity Schema docs | `instructions/docs-import.instructions.md` | `website/docs/**/*.markdown` | The `internal/service/**/*.go` glob
MicrosoftCopilot instructionsmicrosoft/fluentui-system-icons/.github/copilot-instructions.md
build-verify` passes. - Metadata (`metadata.json`) updated if generation logic changed. ## Releases For comprehensive release documentation, including versioning strategy, workflow details, and troubleshooting, see [Release Process Documentation](../docs/releases.md
MicrosoftCopilot instructionsmicrosoft/fast/.github/copilot-instructions.md
This file describes the general instructions for working with the FAST monorepo, including repository structure, code style, tooling, and contribution guidelines.
MicrosoftCopilot instructionsmicrosoft/TinyTroupe/.github/copilot-instructions.md
applyTo: "**" --- # Guidelines for Code Generation in TinyTroupe This document provides the primary guidelines for generating programs in the TinyTroupe project. It is meant to complement any existing documentation or built
MicrosoftCopilot instructionsmicrosoft/GSL/.github/copilot-instructions.md
small and focused with clear preconditions/postconditions - Include comments for complex code, but prefer self-documenting code - Use the Expects() and Ensures() macros for contract verification ### Style Guidelines - Use 4 spaces
MicrosoftCopilot instructionsmicrosoft/vscode-docs/.github/copilot-instructions.md
Code Docs Writing Guidelines Follow the [documentation writing guidelines](instructions/docs-writing.instructions.md) when reviewing or writing documentation
MicrosoftCopilot instructionsmicrosoft/rushstack/.github/copilot-instructions.md
Execute operations affecting the entire repository or multiple projects - Features: - Strict parameter validation and documentation - Support for global and batch commands - Suitable for standardized workflows - Use cases: Dependency installation, building
MicrosoftCopilot instructionsmicrosoft/agent-governance-toolkit/.github/copilot-instructions.md
consistent but externally unverifiable claims (IETF drafts, NIST submissions, patent filings), projects with elaborate documentation but no real users, landing pages with "design partner" CTAs for projects created days
Microsoft AzureCopilot instructionsAzure/Azure-Sentinel/.github/copilot-instructions.md
Analyzer/` in the current branch - This is the normal case when developing/testing - **Never generate documentation here** 2. **Output worktree (publishing CSVs):** `C:\Users\ofshezaf\GitHub\Azure-Sentinel-solution-analyzer-output
Microsoft AzureCopilot instructionsAzure/Azure-Sentinel/Tools/Microsoft-Sentinel-Classic-CLv1-Tables-Impact-Assessment/.github/copilot-instructions.md
github/workflows/update-solution-mapping.yml # Weekly GitHub Action to refresh mapping data LICENSE # MIT License README.md # Full project documentation ``` ## Architecture ### Single-script design The entire tool is a single PowerShell script (`Invoke-TableMigrationReview
FlorianBruniauxCopilot instructionsFlorianBruniaux/claude-code-ultimate-guide/.github/copilot-instructions.md
CHANGELOG.md` under `[Unreleased]` for any file modifications. - Keep changes minimal and aligned with existing documentation style
MicrosoftCopilot instructionsmicrosoft/typespec/.github/copilot-instructions.md
service APIs and shapes. This monorepo contains the TypeSpec compiler, standard library packages, tools, documentation, and various language client emitters. > [!IMPORTANT] > **These instructions do NOT apply to the language emitter
MicrosoftCopilot instructionsmicrosoft/typespec/packages/http-client-js/.github/copilot-instructions.md
require`). - Check that code remains **SOLID** and not over-engineered. - Ensure public functions are documented with JSDoc. - Verify usage of the correct TypeSpec or Alloy-JS APIs (e.g., `$onEmit
Microsoft AzureCopilot instructionsAzure/azure-sdk-for-python/.github/copilot-instructions.md
repeat instructions when guiding users. Users should follow instructions independently.** ### RULE 2: REFERENCE OFFICIAL DOCUMENTATION **ALWAYS** reference the [Azure SDK Python Design Guidelines](https://azure.github.io/azure-sdk/python_design.html) - Link to specific pages
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.
