CodeReview Instructions
Apply this three-phase review protocol. Be adversarial — find how code breaks, not how it works. Never rubber-stamp. Every review must find 3+ issues.
## Phase
correct copyright header:
```csharp
// Copyright (c) Microsoft Corporation.
// Licensed under the MIT License.
```
## CodeReview Rules
### Rule 1: Check for "Kairo" Keyword
- **Description**: Scan code for any occurrence
Flutter, React Native, Unity, and Unreal Engine developers.
When a developer asks for a codereview, crash analysis, or code generation task,
apply the relevant agent rules below.
---
## Agent Rules
exact duplicates.
2. Preserve the recorded service or readiness check, exception cause, status,
error code, request ID, and supported remediation. Translate
implementation-specific exception names into plain language while retaining
microsoft_docs_search, microsoft_docs_fetch, and microsoft_code_sample_search
Note: In Claude Code, the Microsoft Learn MCP server (mcp__claude_ai_Microsoft_Learn_MCP_Server) is also available
functionality by combining simple pieces.
### Quality Checklist
- Can a new team member understand this code in 5 minutes?
- Are names self-explanatory?
- Is the happy path clear and error handling
research-planner, and critical-reviewer.
### Diagram and Table Defaults
**Diagrams:** The default diagram tool is **Mermaid**, which is natively supported by Quarto via ` ```{mermaid} ` code blocks (no extensions or installs
files requires a patch version bump before commit.
- **DO NOT** violate: Never push code to git without completing the full release checklist: (1) bump version in ALL 7 files (package.json
Instructions
Follow these standards when writing or reviewing C# code for this project.
Adhering to these guidelines ensures code consistency, maintainability, and clarity across the team.
## Project Coding Standards
### Comments
does".
```yaml
# ❌ Wrong: describes workflow (agent may follow description instead of reading skill)
description: Codereview between tasks, dispatches subagent per task
# ✅ Correct: triggering conditions only
description: Use when executing
GitHub Copilot Instructions for Agent365-nodejs
## CodeReview Rules
### Rule 1: Check for "Kairo" Keyword
- **Description**: Scan code for any occurrence of the keyword "Kairo"
- **Action**: If "Kairo" is found
missing sessions and return `mcp.NewToolResultError(...)` instead of silently succeeding.
- Keep tests next to the code they validate. Builder packages already contain unit and parity tests; extend those patterns instead