iot
dotnet/iot/.github/copilot-instructions.md
existing pattern does so via an abstraction. - Don't capture `Console` I/O in library code (leave printing/logging to samples/apps). - Don't add hidden thread‑static caches or background threads without
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.
dotnet/iot/.github/copilot-instructions.md
existing pattern does so via an abstraction. - Don't capture `Console` I/O in library code (leave printing/logging to samples/apps). - Don't add hidden thread‑static caches or background threads without
actions/typescript-action/.github/copilot-instructions.md
relevant issues or discussions - Any additional context that may be helpful for reviewers ## Code Review Guidelines When performing a code review, please follow these guidelines: - If there are changes that
kyantech/Palmr/.github/copilot-instructions.md
Commits 8. Push to your fork 9. Create Pull Request targeting the `next` branch ### Code Review - Be responsive to feedback - Keep discussions constructive and professional - Make requested changes promptly
Maintainerr/Maintainerr/.github/copilot-instructions.md
indexes all project docs: implementation guidance, conventions, architecture, and the release-review checklist. Before writing any code, read and follow the standing rules: [.github/instructions/implementation.instructions.md](instructions/implementation.instructions.md) and [.github/instructions/project-notes.instructions.md](instructions/project-notes.instructions.md). Other docs
Steady3 mentions in 2 weeks
No other project uses it yet
nelmio/NelmioApiDocBundle/.github/copilot-instructions.md
Contribution Guidelines: Enhanced Follow these mandatory guidelines when contributing code, documentation, and translations to this repository. All contributions will be reviewed for compliance. --- ## General Project Overview * **Project Scope:** This
Steady16 mentions in 2 weeks
No other project uses it yet
mampfes/hacs_waste_collection_schedule/.github/copilot-instructions.md
sources on `master`; for new pipeline sources use the release branch guide above. ## Things reviewers consistently reject - Hardcoded dates or weekday rules — sources must fetch from a real upstream
zhaohongxuan/obsidian-weread-plugin/.github/copilot-instructions.md
WeRead (微信读书) book metadata, highlights, notes, and reviews into Markdown files in an Obsidian vault. - The plugin supports login via WeChat QR code, cookie management, custom templates (Nunjucks), and flexible
Steady7 mentions in 2 weeks
No other project uses it yet
reubeno/brush/.github/copilot-instructions.md
implementation-and-provenance) required by `AGENTS.md`. Apply it to delegated agents and their tools. ## Code Review Checklist When reviewing PRs, verify: - [ ] **Documentation**: All exported APIs have rustdoc comments (missing docs
mfem/mfem/.github/copilot-instructions.md
examples, tests, build or docs changes, and downstream APIs. 4. Analyze the code against the critical review pillars. 5. Compare the change against nearby code and MFEM patterns; flag unmotivated
timeplus-io/proton/.github/copilot-instructions.md
claude/skills/build-and-verify/SKILL.md` for build, compile, run, and test tasks - Use `.claude/skills/cpp-coding/SKILL.md` for C++ code changes and reviews - Use `.claude/skills/sql-usage/SKILL.md` for streaming SQL work - Use `.claude/skills/review/SKILL.md` for PR or diff review
kubeflow/trainer/.github/copilot-instructions.md
GitHub Copilot Code Review Instructions ## Review Philosophy - Only comment when you have HIGH CONFIDENCE (>80%) that an issue exists - Be concise: one sentence per comment when possible - Focus on actionable
Steady5 mentions in 2 weeks
No other project uses it yet
home-assistant/supervisor/.github/copilot-instructions.md
code, comments, and documentation. ## AI policy This project follows the [Open Home Foundation AI Policy](../AI_POLICY.md). Autonomous contributions are not accepted: a human must review, understand, and be able
alibaba/loongcollector/.github/copilot-instructions.md
part of the full suite 4. Coverage reporting is available through make targets ## Code Review Rule 你是一个高级代码审查助手,审查代码时要从QA角度仔细检查问题,以批判的眼光看待代码,以发现潜在问题为目的。 为了避免得到假阳性的检查结果,请注意: - 分析具体代码片段时要包含足够上下文,不要仅基于局部信息做出判断。 - 避免基于记忆进行代码分析,必须基于实际查看的代码。 - 在指出问题前,先理解业务逻辑的完整流程,考虑代码设计的合理性和必要性。 针对每个有变更的文件及其差异块
zeroc-ice/ice/.github/copilot-instructions.md
branches. Breaking change(s): - [Description of the breaking change] ``` ## Changelog Validation **When reviewing PRs, check if code changes have a changelog fragment under `changelog.d/`.** Changelog entries are added as fragment
microsoft/DirectXTex/.github/copilot-instructions.md
ERROR_FILE_TOO_LARGE)` | | `HRESULT_E_CANNOT_MAKE` | `HRESULT_FROM_WIN32(ERROR_CANNOT_MAKE)` | ## Code Review Instructions When reviewing code, focus on the following aspects: - Adherence to coding standards defined
aagentah/nw_wrld/.github/copilot-instructions.md
clear regression risk**. - If you are not confident it is must-fix, **stay silent**. #### Review priorities (in order) 1. **Behavior safety** - For valid inputs, changes should
dotnet/android/.github/copilot-instructions.md
initialize `TaskEnvironment` to `Fallback` when implementing the interface directly so direct instantiation also works. - Review helpers, exception paths, and static state for thread safety. Do not mutate shared process state
devcontainers/images/.github/copilot-instructions.md
Copilot Code Review - Every image change in a contributor PR requires a manifest bump. For breaking changes such as a base OS change, increment the major component and reset minor
chi111i/BypassAIGC/.github/copilot-instructions.md
Copilot Code Review Instructions 请始终使用简体中文进行代码审查。 审查目标不是给出泛泛的风格建议,而是尽早发现会破坏项目的真实问题。优先指出阻塞合并的问题,并按严重程度排序。 ## 审查优先级 优先检查以下问题: - 破坏现有功能、调用链、接口契约或用户流程的改动。 - 前端和后端 API 契约不一致,例如认证方式、请求参数、响应字段、SSE、下载 URL。 - 认证、鉴权、用户隔离、管理员接口、token、卡密兼容逻辑中的安全或兼容性问题。 - 并发控制
oss-review-toolkit/ort/.github/copilot-instructions.md
When performing a code review on a pull request, verify the following things: * there is no merge commit among the commits of the pull request, * the commit messages use American
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.