How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
MicrosoftCopilot instructionsmicrosoft/WindowsProtocolTestSuites/.github/copilot-instructions.md
suite architecture with shared infrastructure. IMPORTANT : DO A DEEP SCAN ON THE CODE BASE DOCUMENTATION STORED IN THE AI-DOCS (ai-docs) FOLDER ## Architecture ### Core Components - **ProtoSDK**: Protocol library with
MicrosoftCopilot instructionsmicrosoft/mscclpp/.github/copilot-instructions.md
Project Contribution Guidelines This document outlines a few useful informations for contributing to this project. ## C/C++ Headers Layout This project has two C/C++ header directories: `include/mscclpp/` and `src/include/`. Headers
MicrosoftCopilot instructionsmicrosoft/pxt-arcade/.github/copilot-instructions.md
semantic versioning for all packages - Maintain backward compatibility when possible - Write clear, self-documenting code with JSDoc comments - Follow the existing code style and patterns in each component ### Code Generation
nodetool-aiCopilot instructionsnodetool-ai/nodetool/.github/copilot-instructions.md
Clean up subscriptions/timers in afterEach - [ ] Test error states - [ ] Test loading states - [ ] Test edge cases ## Documentation Add JSDoc comments for complex functions: ```typescript /** * Calculates the optimal layout for nodes
MicrosoftCopilot instructionsmicrosoft/react-native-windows-samples/.github/copilot-instructions.md
examples │ └── ContinuousIntegration/ # CI/CD pipeline configurations ├── samples-old/ # Legacy samples for older RN versions ├── website/ # Documentation website (Docusaurus) ├── docs/ # Additional documentation └── .github/ # GitHub workflows and templates ``` ## Technology Stack - **React Native
gitmono-devCopilot instructionsgitmono-dev/mega/.github/copilot-instructions.md
avoid unwrap()/expect() in library code except in tests or when invariant-proofed and documented. - Prefer iterator and slice APIs to heap-allocating vectors in hot paths. Use SmallVec, bytes
MicrosoftCopilot instructionsmicrosoft/AL-Go/.github/copilot-instructions.md
Windows (PowerShell 5) and Linux (PowerShell 7). - Use `InModuleScope` for testing private module functions. ## Documentation Requirements - All new or modified AL-Go settings must be: - Documented in `Scenarios/settings.md` with
MicrosoftCopilot instructionsmicrosoft/PowerAppsCodeApps/samples/FluentSample/.github/copilot-instructions.md
parts of the system—downstream dependencies, shared services, and global logic should be reviewed. - Document or summarize your reasoning and decision-making if a change affects multiple components. --- # Using this
IvanWng97Copilot instructionsIvanWng97/pixtuoid/.github/copilot-instructions.md
architecture invariants and "known sharp edges" — much of what looks like a bug is documented, load-bearing design. Path-scoped Rust standards: [`.github/instructions/rust.instructions.md`](instructions/rust.instructions.md). Workflow + how to add a theme
ZaxbyHubCopilot instructionsZaxbyHub/opencode-swarm/.github/copilot-instructions.md
validation required by `.claude/skills/commit-pr/SKILL.md` (Step 3). At minimum, do not publish without documenting: - build result (including `git diff --exit-code -- dist/`) - typecheck result - formatting/lint result (`bunx biome ci .`) - relevant unit
MicrosoftCopilot instructionsmicrosoft/PSRule/.github/copilot-instructions.md
project includes .NET libraries, a PowerShell module, CLI tools, VS Code extension, and comprehensive documentation. ### Bootstrap and Build Process 1. **Install PowerShell dependencies** (3 seconds, NEVER CANCEL): ```bash pwsh ./scripts/pipeline-deps.ps1
MicrosoftCopilot instructionsmicrosoft/Qcodes/.github/copilot-instructions.md
configuration for the package and for the tools we use lives in ``pyproject.toml``. Documentation, in the ``docs/`` folder, is written using Restructured Text or Jupyter Notebook formats, and sphinx
MicrosoftCopilot instructionsmicrosoft/Power-CAT-Copilot-Studio-Kit/.github/copilot-instructions.md
React 19 + Fluent UI v9 + TypeScript) and deployed from `docs/` on the `feature/github-pages-agent` branch. - **Documentation** under `docs/` (the landing-page assets) and other top-level `.md` files. ## Most tasks fall
GitHubCopilot instructionsgithub/local-action/.github/copilot-instructions.md
coding conventions and best practices - Changes should maintain consistency with existing patterns and style - Document changes clearly and thoroughly, including updates to existing comments when appropriate - Do not include basic
MicrosoftCopilot instructionsmicrosoft-foundry/foundry-samples/.github/copilot-instructions.md
following text to your review: 🛑STOP! This PR contains changes that may break documentation. Please post a message on [ai-platform-docs](https://teams.microsoft.com/l/team/19%3AHhf4F_YfPn3kYGdmWvePNwlbF5-RR8wciQEUwwrcggw1%40thread.tacv2/conversations?groupId=fdaf4412-8993-4ea6-a7d4-aeaded7fc854&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47) to request help. Only files
Sidiora-LabsCopilot instructionsSidiora-Labs/LayerX-Network/.github/copilot-instructions.md
historical gate matrices. - **Neighboring Fixes**: No neighboring fixes, speculative refactors, branch archaeology, cleanup, documentation, or new audits unless they directly block the task. - **Repeated Unchanged**: No repeated unchanged test. Maximum
Microsoft AzureCopilot instructionsAzure/PSRule.Rules.Azure/.github/copilot-instructions.md
release schedule use the next quarter based on the current date. - Use the documentation in `docs/license-contributing/metadata-reference.md` to determine the correct metadata tags and labels for rules. File Management Context
MicrosoftCopilot instructionsmicrosoft/PowerApps-Tooling/.github/copilot-instructions.md
central entry point, built on YamlDotNet. Uses strongly-typed models like `NamedObject ` for YAML document structure. The models in `src\Persistence\PaYaml\Models\SchemaV3\**` represent the 'Source Code' schema
Microsoft AzureCopilot instructionsAzure/azure-container-networking/.github/copilot-instructions.md
needs `systemcrypto`, CGO=0 needs `ms_nocgo_opensslcrypto`. Go 1.27+ changes these rules. ## AI Documentation See `.github/AI-DOCS.md` for details on how AI instruction files are structured in this repo
MicrosoftCopilot instructionsmicrosoft/go/.github/copilot-instructions.md
This way we catch regressions."* - **`go/src/go/build/deps_test.go`**: Update if adding new package dependencies. ### 8. Update documentation - Add the new algorithm's platform support status to `eng/_util/cmd/updatecryptodocs/docs.go`, then regenerate the doc: ```bash
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.
