garnet
microsoft/garnet/.github/copilot-instructions.md
# Garnet - Copilot Instructions Garnet is a high-performance remote cache-store from Microsoft Research
How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
microsoft/garnet/.github/copilot-instructions.md
# Garnet - Copilot Instructions Garnet is a high-performance remote cache-store from Microsoft Research
microsoft/winget-pkgs/.github/copilot-instructions.md
files describing how to install Windows applications via `winget`. There is no application source code here. The tooling is PowerShell scripts in `Tools/`. ## ⚠️ Critical Performance Rule **Never recursively scan
hashicorp/terraform-provider-aws/.github/copilot-instructions.md
only. Detect AWS API exceptions with `errs.IsA[*awstypes. ]`. ## Review tone Be specific and actionable. Cite the rule and propose the corrected code. Focus on substance over style: avoid minor comments
omnigent-ai/omnigent/.github/copilot-instructions.md
Copilot Code Review Instructions ## E2E Test Requirement Every pull request that introduces a new feature **must** include at least one end-to-end (e2e) test covering the happy-path behaviour
microsoft/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
microsoft/agent-governance-toolkit/.github/copilot-instructions.md
erodes trust. ## PR Review — Mandatory Before Merge NEVER merge a PR without thorough code review. CI passing is NOT sufficient. ### Review Output Style All PR reviews (human and bot) MUST
Azure/Azure-Sentinel/Tools/Microsoft-Sentinel-Classic-CLv1-Tables-Impact-Assessment/.github/copilot-instructions.md
refresh mapping from upstream CSVs .github/copilot-instructions.md # This file — global Copilot context .github/instructions/powershell.instructions.md # PowerShell-specific coding conventions .github/agents/sentinel-migration-assistant.md # Copilot custom agent for guided execution .github/workflows/update-solution-mapping.yml # Weekly GitHub Action to refresh mapping
microsoft/typespec/packages/http-client-js/.github/copilot-instructions.md
blocks in vitest. - !NEVER modify existing ts or tsp code blocks --- ## 3. Code Review Instructions - **Review Criteria** - Confirm ES Module usage (no `require`). - Check that code remains **SOLID
Azure/azure-sdk-for-python/.github/copilot-instructions.md
user for clarification if repository path or configuration file is ambiguous. --- ## MGMT SDK Code Review Rules ### SCOPE These rules apply to management-plane SDK packages located at `sdk/*/azure-mgmt-*/`. ### REVIEW
github/gh-aw/.squad/templates/copilot-instructions.md
starting work, check your capability profile in `.squad/team.md` under the **Coding Agent → Capabilities** section. - **🟢 Good fit** — proceed autonomously. - **🟡 Needs review** — proceed, but note in the PR description that a squad
vitali87/code-graph-rag/.github/copilot-instructions.md
Code review guidelines When reviewing pull requests: - Only leave comments for critical, major, or high-severity issues: logic bugs, security vulnerabilities, data loss or corruption, race conditions, and breaking
microsoft/fluentui-blazor/.github/copilot-instructions.md
existing enum implementation style (XML docs + Description attributes). ## Skills - When writing, reviewing, or refactoring C# / .NET / Blazor code, or when authoring unit tests with xUnit and bUnit, load and follow
microsoft/WindowsAppSDK/.github/copilot-instructions.md
Windows App SDK AI contributor guidance
microsoft/PyRIT/.github/copilot-instructions.md
before adding or reviewing components so new code lands in the right place. ## Code Review Guidelines When performing a code review, be selective. Only leave comments for issues that genuinely
modelcontextprotocol/csharp-sdk/.github/copilot-instructions.md
signed off on the notes — the published notes then stand as their own reviewed work. Removing it is always the user's decision; never remove it on your own initiative
crmne/ruby_llm/.github/copilot-instructions.md
AGENTS.md` and `CONTRIBUTING.md` as the source of truth for every change, review, and triage. `AGENTS.md` describes how the code is built and the boundaries `Archspec.rb` enforces; `CONTRIBUTING.md` describes what
microsoft/FLAML/.github/copilot-instructions.md
reruns-delay 10` for flaky tests ### Coverage - Aim for good test coverage on new code - Coverage reports are generated for Python 3.11 builds - Coverage reports are uploaded to Codecov
microsoft/ApplicationInspector/.github/copilot-instructions.md
Linux, and macOS 5. **Resource cleanup**: Properly dispose of file handles and other resources ## Code Review Checklist Before submitting changes: - [ ] Code builds without errors (`dotnet build`) - [ ] All tests pass (`dotnet
mongodb/mongo-python-driver/.github/copilot-instructions.md
When reviewing code, focus on: ## Security Critical Issues - Check for hardcoded secrets, API keys, or credentials. - Check for instances of potential method call injection, dynamic code execution, symbol injection
IvanMurzak/Unity-MCP/.github/copilot-instructions.md
library usage, which is an external dependency specifically designed for reflection-based access patterns. ## Code Review Before performing any code review, you **MUST** read the project constitution: [`.specify/memory/constitution.md`](.specify/memory/constitution.md
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.