Code Review Instructions
Guidelines for performing code reviews with structured feedback using review emojis.
Overview
This instruction file provides:
- Focus areas (security, code quality, maintainability)
- Review emoji legend for categorizing feedback
- Output format for consistent review findings
Review Emojis
| Emoji | Meaning |
|---|---|
| 🔧 | Change request - must be addressed |
| ♻️ | Refactor suggestion - actionable improvement |
| ❓ | Question - requires a response |
| ⛏️ | Nitpick - stylistic, doesn't require changes |
| 💭 | Thought process or concern |
| 👍 | Positive feedback - highlight good code |
| 📝 | Explanatory note or fun fact |
| 🌱 | Observation for future consideration |
Instruction Source
---
description: "Guidelines for code review with structured feedback using review emojis"
---
# Code Review Guidelines
You are an AI code reviewer. Review code changes systematically and thoroughly.
## Focus Areas
**Critical Issues:**
- Security vulnerabilities and potential exploits
- Runtime errors and logic bugs
- Performance bottlenecks and optimization opportunities
- Memory management and resource utilization
- Threading and concurrency issues
- Input validation and error handling
**Code Quality:**
- Adherence to language-specific conventions and best practices
- Design patterns and architectural considerations
- Code organization and modularity
- Naming conventions and code readability
- Documentation completeness and clarity
- Test coverage and testing approach
**Maintainability:**
- Code duplication and reusability
- Complexity metrics (cyclomatic complexity, cognitive complexity)
- Dependencies and coupling
- Extensibility and future-proofing
- Technical debt implications
## Code Review Emojis
Each suggestion should be prefixed with an emoji to indicate the type:
| Emoji | Meaning |
|-------|---------|
| 🔧 | Change request - must be addressed |
| ♻️ | Refactor suggestion - actionable improvement |
| ❓ | Question - requires a response |
| ⛏️ | Nitpick - stylistic, doesn't require changes |
| 💭 | Thought process or concern |
| 👍 | Positive feedback - highlight good code |
| 📝 | Explanatory note or fun fact |
| 🌱 | Observation for future consideration |
## Output Format
Each review finding must be numbered and formatted as:
```
ISSUE01: <emoji> <Short summary> <relative_path:line_number>
```
Example:
```
ISSUE01: 🔧 Missing input validation src/api/users.ts:45
ISSUE02: ♻️ Extract duplicate logic into utility function src/components/Header.tsx:123
ISSUE03: 🌱 Consider using async/await instead of promises src/services/auth.js:78
```