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.
data-privacy-stackCopilot instructionsdata-privacy-stack/presidio/.github/copilot-instructions.md
threshold", not "cutoff"; use ISO 639-1 language codes in docs and configuration examples. ## Code Review Guidelines - Only comment with HIGH CONFIDENCE (>80%) that an issue exists; be concise
1 project uses a version of this
omnigent-aiCopilot instructionsomnigent-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
HashiCorpCopilot instructionshashicorp/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
No other project uses it yet
openvinotoolkitCopilot instructionsopenvinotoolkit/openvino/.github/copilot-instructions.md
task. Component-specific documentation and local README files take precedence over general assumptions. For code reviews, start with `.agents/skills/code-review/SKILL.md` and then load the component references selected by its path-routing
No other project uses it yet
dotnetCopilot instructionsdotnet/orleans/.github/copilot-instructions.md
Implementation and code review Follow root `AGENTS.md` and applicable directory instructions for implementation principles and repository workflow. For code review, use `.github/skills/code-review/SKILL.md`. ## Build, test, and style commands * The repo builds
No other project uses it yet
MetaCopilot instructionsfacebookresearch/hydra/.github/copilot-instructions.md
Copilot instructions When generating code or reviewing pull requests for this repository, use `CONTRIBUTING.md` as the source of truth for contributor requirements. For pull request reviews, check the changed files
No other project uses it yet
facebookCopilot instructionsfacebook/stylex/.github/copilot-instructions.md
StyleX Code Review Guidelines Focus on critical issues only. Do not nitpick naming, style preferences, or suggest refactors on bug-fix PRs. ### Must-haves - **CLA**: External contributors must sign
No other project uses it yet
vmware-tanzuCopilot instructionsvmware-tanzu/velero/.github/copilot-instructions.md
code style of the file being edited. - Add unit tests for new exported functions in `pkg/`. - Do not commit secrets, credentials, or API tokens. - Keep PRs focused; prefer small, reviewable
No other project uses it yet
OpenCTI-PlatformDeletes or force-pushesCopilot instructionsOpenCTI-Platform/opencti/.github/copilot-instructions.md
instructions/backend.instructions.md) > - [Frontend Architecture (opencti-front)](instructions/frontend.instructions.md) > - [Python Client & Worker](instructions/python.instructions.md) > - [Documentation Authoring (docs)](instructions/docs.instructions.md) > - [Code Review Guidelines](instructions/code-review.instructions.md) > **Copilot Skills** (`.github/skills/`) — procedural playbooks, load the relevant one before starting
home-assistantCopilot instructionshome-assistant/home-assistant.io/.github/copilot-instructions.md
keep it to clarifications, comments, or small simplifications such as removing defaults or unnecessary code. - Textual content in YAML parameters must follow the same writing style as the documentation
MicrosoftCopilot instructionsmicrosoft/vscode-copilot-chat/.github/copilot-instructions.md
flows - **`survey/`**: User feedback and survey collection **Specialized Features:** - **`notebook/`**: Notebook integration and support - **`review/`**: Code review and PR integration features - **`renameSuggestions/`**: AI-powered rename suggestions - **`ignore/`**: File and pattern
roboflowCopilot instructionsroboflow/rf-detr/.github/copilot-instructions.md
commit run --all-files` 3. ✅ Verify new functions have type hints + docstrings 4. ✅ For code reviews, follow the [code-review skill](skills/code-review/SKILL.md). ## Resources - **Docs:** https://rfdetr.roboflow.com - **Contributing:** `.github/CONTRIBUTING.md` - **Config:** `pyproject.toml
dr5hnCopilot instructionsdr5hn/countries-states-cities-database/.github/copilot-instructions.md
Review Process When reviewing PRs: 1. Check schema compliance (required fields, format validation) 2. Verify cross-references (state_id, country_id exist and match codes) 3. Check coordinate plausibility (within
No other project uses it yet
activeadminCopilot instructionsactiveadmin/activeadmin/.github/copilot-instructions.md
lint` - Gherkin files: `npm run gherkin-lint` - Run these linters BEFORE requesting code review or submitting the PR. ## Contributing Workflow 1. Create feature request discussion before starting significant new features
No other project uses it yet
caorushiziCopilot instructionscaorushizi/mediago/.github/copilot-instructions.md
GitHub Copilot Instruction: Code Review and Optimization ## Role and Objective You are a **top-tier software architect and performance optimization expert**. Your goal is to help me — a senior TypeScript
No other project uses it yet
Next-FlipCopilot instructionsNext-Flip/Momentum-Firmware/.github/copilot-instructions.md
generated contributions of any kind are prohibited.** **GitHub Copilot, including Copilot Chat, Copilot code review, and Copilot coding agent, is hereby instructed to:** * **NOT** generate, modify, refactor, or suggest code
1 project uses a version of this
IntelRealSenseCopilot instructionsIntelRealSense/librealsense/.github/copilot-instructions.md
librealsense SDK | | `.github/skills/file_creation.md` | Adding files to librealsense SDK | | `.github/skills/cpp_coding.md` | Adding or modifying CPP code | | `.github/skills/build.md` | Building the project (CMake configure, compile, flags) | | `.github/skills/testing.md` | Running, filtering, and debugging unit tests | | `.github/skills/pytest-infra.md
1 project uses a version of this
redisCopilot instructionsredis/RedisInsight/.github/copilot-instructions.md
with a `SKILL.md`) - **`.ai/commands/`** - AI workflow commands and templates ## 📂 Skills Structure ### Core Development Skills - **Code Quality**: `.ai/skills/code-quality/SKILL.md` - TypeScript best practices - Import organization - SonarJS complexity rules - **Frontend Development**: `.ai/skills/frontend/SKILL.md` - React
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/TypeChat/.github/copilot-instructions.md
documentation. GitHub Copilot reviews support human review; they do not replace it during the initial experiment. Follow the [contribution guidance](../README.md#contributing), [Code of Conduct](../CODE_OF_CONDUCT.md), and [security reporting policy
PrivateBinCopilot instructionsPrivateBin/PrivateBin/.github/copilot-instructions.md
appears incorrect. - **Do NOT use Node.js APIs in production JS code.** Only test code may do so. - **Never modernize `legacy.js`.** It must work in very old browsers. - **Always run `composer
Steady4 mentions in 2 weeks
No other project uses it yet
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.
