openmc
openmc-dev/openmc/.github/copilot-instructions.md
When reviewing code changes in this repository, use the `reviewing-openmc-code` skill
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.
openmc-dev/openmc/.github/copilot-instructions.md
When reviewing code changes in this repository, use the `reviewing-openmc-code` skill
RocketPy-Team/RocketPy/.github/copilot-instructions.md
pytest` - `make pytest-slow` - `make coverage` - `make coverage-report` - `make build-docs` - Before finishing code changes, run focused tests first, then broader relevant suites. - When running Python directly in this
FalkorDB/QueryWeaver/.github/copilot-instructions.md
allow external MCP clients to call QueryWeaver's Text2SQL operations. Key points for coding agents and reviewers: - Runtime toggle: the built-in MCP endpoints can be disabled with
No other project uses it yet
openops-cloud/openops/.github/copilot-instructions.md
following instructions are only to be applied when performing a code review. # Pull Request Review Guidelines Review the current pull request diff for security, code quality/readability, performance, test coverage
MicrosoftDocs/windows-driver-docs/.github/copilot-instructions.md
that domain. ## Contributing See [CONTRIBUTING.md](CONTRIBUTING.md) for detailed contribution guidelines, including: - Pull request process - Code review requirements - Microsoft Contributor License Agreement (CLA) - Style guide adherence
python-semantic-release/python-semantic-release/.github/copilot-instructions.md
steps that the developer generally has to do. This includes generating changelogs, stamping the code with version strings, creating a repository tag and annotating releases on a remote Git server
Steady8 mentions in 2 weeks
No other project uses it yet
nextcloud/mail/.github/copilot-instructions.md
Copilot Code Review Instructions ## Scope Only review for the following: - **Bugs** - **Security**: Injection vulnerabilities (SQL, command, XSS), hardcoded secrets or credentials, insecure deserialization, broken auth, path traversal, unsafe
microsoft/testfx/.github/copilot-instructions.md
accessors. - IMPORTANT: Make sure to apply this rule strictly both during PR review and when working on code changes. - Every API marked with `[Experimental]` MUST include this sentence
web-infra-dev/rslib/.github/copilot-instructions.md
Copilot code review instructions ## Purpose Use these instructions for pull request review in this repository. Focus on recurring, reusable review logic that prevents regressions. ## Instruction style - Write short, imperative feedback
landing-ai/ade-python/.github/copilot-instructions.md
drift and AI no-ops legitimately produce a mechanical-only PR. When performing a code review on these PRs: - Review the PR **in its current state, as a whole
sheepzh/time-tracker-4-browser/.github/copilot-instructions.md
When performing a code review, follow [code-review.md](./instructions/code-review.md) for guidance
ChenyCHENYU/Robot_Admin/.github/copilot-instructions.md
# 🤖 Robot Admin — AI 编码指南 > **本文件面向 AI 编程助手**(Copilot / Cursor / Claude 等)。 > 在对本项目生态进行任何代码生成、修改或建议之前,**必须完整阅读本指南
NVIDIA/cudf-spark/.github/copilot-instructions.md
memory allocation semantics, null handling) - **NVIDIA/cudf-spark-jni** — verify JNI binding signatures, memory ownership rules, error codes ## Review Checklist - [ ] C1: Resource leaks — AutoCloseable not closed on exception paths; use withResource/closeOnExcept/safeClose, never bare
microsoft/DevSkim/.github/copilot-instructions.md
target the `main` branch 3. PRs require: - Changelog.md update - Passing CI/CD checks - Code review approval 4. Merges use **squash merge** strategy ## Additional Resources - [Build from Source](https://github.com/microsoft/DevSkim/wiki/Build-from-Source) - [Writing
zetaloop/desktop/.github/copilot-instructions.md
secrets, passwords, or sensitive data** - **Validate and sanitize user input** - **Follow secure coding practices**: Review code for XSS, injection, and other vulnerabilities - **Report security issues**: Use private vulnerability reporting
urzeye/ophel/.github/copilot-instructions.md
Ophel — Copilot Repository Instructions ## Language When performing a code review, respond in Chinese (Simplified). All review comments, suggestions, and explanations must be written in Simplified Chinese. ## Project Overview Ophel
moodlehq/moodleapp/.github/copilot-instructions.md
built 6. **Do** use `CoreSitesReadingStrategy` when fetching data to control cache vs network behavior ## Code reviews - When performing a code review, check that the language is in British English
dotnet/SqlClient/.github/copilot-instructions.md
review, ensuring they follow project conventions and include necessary tests and documentation. - **Code Reviews**: Review PRs from other contributors, providing feedback and suggestions for improvements. - **Continuous Improvement**: Identify areas
dotnetfactory/fluid-calendar/.github/copilot-instructions.md
GitHub Copilot Instructions for FluidCalendar These are repository-wide instructions for GitHub Copilot's coding agent. They are a condensed mirror of `CLAUDE.md` and `openspec/project.md`; when anything here is ambiguous
iovisor/ubpf/.github/copilot-instructions.md
linting (shellcheck) - C++ linting (cpplint) - Python linting (pylint) - Trailing whitespace and EOF fixes ## Copilot Code Review - When performing a pull request or normal code review for this repository
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.