Review guidance for ESPHome pull requests. Use this when reviewing a pull request that changes ESPHome Python, C++, or component code, to check it against the project's coding conventions, embedded-systems memory rules, testing requirements, and breaking-change policy.
Review OpenVINO changes for correctness, compatibility, performance, security, testing, and maintainability. Use when reviewing a pull request or proposed diff.
Review Orleans changes for layer contracts, invariants, minimal complexity, runtime performance, testing, and focused documentation. Use for GitHub Copilot code review and other review tasks.
Kyverno-specific review guidance for pull requests. Use whenever reviewing a PR against kyverno/kyverno — points to the project's real review checklist and per-package context instead of generic review practice.
Review staged and unstaged code changes for FastLED coding standards violations, span usage mandates, and example quality. Use after making code changes to ensure compliance.
Performs a multi-axis code review (correctness, readability, architecture, security, and performance) before merge. Use when reviewing GitHub PRs, your own code, another agent's, or a human's, or when assessing quality before the main branch. Triggers on code-review, /code-review, PR review.
Reviews code changes using CodeRabbit AI. Use when user asks for code review, PR feedback, code quality checks, security issues, or requests fix-review cycles.
Review a GitHub pull request or requested local diff for problems. Use when asked to review a PR, do a code review, check a PR for issues, or review local changes. Focuses only on identifying problems — not style nits or praise.
MUST USE for every Azure SDK for .NET code review. WHEN: review this PR or pull request; review my changes, diff, patch, or commit; API review; pre-PR review; automatic GitHub Copilot review. Performs open-ended bug, security, correctness, reliability, and maintainability analysis plus Azure SDK API design, analyzer, packaging, testing, documentation, and generated-code checks. Applies management-plane guidance per owning library.
Review code, PRs, diffs, and changes in the Pebble codebase for correctness issues including resource leaks, concurrency bugs, iterator misuse, and lint violations. Use when asked to review code, a pull request, diff, or changes.
Adversarially review pull requests and code changes against the actual problem. Use for GitHub Copilot code review to assess correctness, root cause, simplicity, deletions, test quality, maintainability, and merge readiness.
Review TypeSpec pull requests against the project's own rules: the Tier 0-3 breaking change policy, `.chronus` changelog requirements, compiler API usage, test framework conventions, and emitter output stability. Use when reviewing a diff or pull request in this repository.
Reviews code changes and provides actionable feedback. Use when the user asks to review a PR, diff, commit, or code changes. Triggers on "/review", "review this PR", "review my changes", "code review".
Review pull requests and code changes in the Azure SDK for Python repository. USE FOR: GitHub Copilot code review; CCR; review pull request; review PR; review diff; find bugs or regressions introduced by a PR; cross-package SDK review. Finds high-confidence correctness, security, API compatibility, dependency, documentation, and test issues. DO NOT USE FOR: implementing fixes; running tests; fixing CI; releases; APIView feedback.
Review Grafana Tempo pull requests for correctness, data integrity, performance, API and config design, and testing. Use for Copilot code reviews and re-reviews, reporting actionable findings without approval or merge recommendations.
Review code changes in Swashbuckle.AspNetCore for correctness, OpenAPI fidelity, compatibility, performance, and consistency with project conventions. Use when reviewing PRs or code changes.
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.