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.
harvesterCopilot instructionsharvester/harvester/.github/copilot-instructions.md
platform. See `AGENTS.md` for full project context, repo structure, and build commands. When reviewing code, use the conventions outlined below to ensure consistency and maintainability. Pay particular attention
tixl3dCopilot instructionstixl3d/tixl/.github/copilot-instructions.md
endings were munged — fix the working tree and `commit --amend`. ## Review and Quality Expectations - Point out obvious bugs, misleading code, incorrect implementations, and typos - Fix spelling mistakes in touched comments
Steady2 mentions in 2 weeks
No other project uses it yet
nginxCopilot instructionsnginx/kubernetes-ingress/.github/copilot-instructions.md
pipelines` | Review | Working on CI workflows, build matrices, or release pipeline | | `nic-code-review` | Review | Reviewing PRs (local chat, `pr-review` prompt, GitHub Copilot Code Review bot) | | `nic-contribution-review
xvzcCopilot instructionsxvzc/spoofdpi/.github/copilot-instructions.md
Senior Go Backend Engineer and Security Auditor. Review the following code with a strict focus on **CRITICAL BUGS** and **STABILITY ISSUES**. **🚫 IGNORE the following (Do NOT report):** - Coding style, formatting
MicrosoftCopilot instructionsmicrosoft/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
Steady10 mentions in 2 weeks
No other project uses it yet
hyperlight-devCopilot instructionshyperlight-dev/hyperlight/.github/copilot-instructions.md
logical order. * Rebase your branch on `main`. No merge commits. * Label PRs per `docs/github-labels.md`. ## Reviewing code When reviewing a diff (your own or a PR), weight these for Hyperlight: * Correctness
No other project uses it yet
dotnetCopilot instructionsdotnet/docs/.github/copilot-instructions.md
usage` value when suggesting editorial-based corrections, when reviewing a pull request, or when reviewing article - Don't apply the `ai-usage` metadata to files in the .github folder
clshortfuseCopilot instructionsclshortfuse/renodx/.github/copilot-instructions.md
find the matching skill and read its `SKILL.md` before acting. When performing a Copilot code review, apply the RenoDX review checklist in `.github/instructions/renodx-code-review.instructions.md` and the review-focused skill in `.github/skills/code-review/SKILL.md
MicrosoftCopilot instructionsmicrosoft/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
No other project uses it yet
sebastienrosCopilot instructionssebastienros/jint/.github/copilot-instructions.md
change it. Nothing is repeated here on purpose. Copilot's cloud agent and Copilot code review read `AGENTS.md` directly, and the cloud agent additionally picks up the nested ones
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/WindowsAppSDK/.github/copilot-instructions.md
Windows App SDK AI contributor guidance
NewFutureCopilot instructionsNewFuture/DDNS/.github/copilot-instructions.md
Implement the complete change: code, tests, schema/metadata, Chinese docs, and English docs where applicable. 5. Run focused checks, then the full affected suite. 6. Self-review the diff and continue
Model Context ProtocolCopilot instructionsmodelcontextprotocol/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
No other project uses it yet
IvanMurzakCopilot instructionsIvanMurzak/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
Steady7 mentions in 2 weeks
No other project uses it yet
kubernetes-sigsCopilot instructionskubernetes-sigs/agent-sandbox/.github/copilot-instructions.md
Code Review Guidelines **Project Context & Architecture:** Refer to [AGENTS.md](../AGENTS.md) for full project background, module layout, toolchain versions, and core conventions. **Scope of Review:** Focus strictly on substantive findings tied
No other project uses it yet
kstenerudCopilot instructionskstenerud/KSCrash/.github/copilot-instructions.md
GitHub Copilot Code Review Instructions for KSCrash When performing code reviews on this repository, follow these instructions to identify API breaking changes in the KSCrash crash reporting library. ## Scope
Steady2 mentions in 2 weeks
No other project uses it yet
crmneCopilot instructionscrmne/ruby_llm/.github/copilot-instructions.md
pull request for anything beyond a small fix, so CodeRabbit and GitHub code scanning review it first. Merge your own pull request (squash) once CI is green and those reviews
dvorkaCopilot instructionsdvorka/hstr/.github/copilot-instructions.md
review. ## Security instructions - ALWAYS follow security best practices. - NEVER log form data that may contain sensitive information. - ALWAYS consider overflow and memory corruption issues when writing C code. ## Backend code
CysharpCopilot instructionsCysharp/MagicOnion/.github/copilot-instructions.md
Project Custom Instructions ## Coding Review Guidelines When reviewing code, focus on the following points: - Use of Modern C# Features - Consider using the latest syntax available (C# 13 or later), such
wmariussCopilot instructionswmariuss/awesome-devops/.github/copilot-instructions.md
list entry with code or workflow changes. - Flag any change to `.github/copilot-instructions.md`, `.github/instructions/`, `AGENTS.md`, `website/scripts/review/` or `.github/workflows/` for maintainer attention. These control automated review and deployment; a contributor adding
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.
