code-review

name	Code Review
description	Review code for quality, security, and style with structured feedback
version	1.0
tags	["engineering","quality"]
requires_tools	["mcp:filesystem:*"]

Process

1. Read the target file(s) using the filesystem tools
2. Security check: Look for SQL injection, XSS, command injection, hardcoded secrets, unsafe deserialization
3. Code quality: Check naming conventions, function length, duplication, complexity
4. Error handling: Verify edge cases, null checks, proper exception handling
5. Style & readability: Consistent formatting, meaningful comments, clear variable names
6. Performance: Identify obvious inefficiencies, unnecessary loops, memory issues

Output Format

Provide structured feedback using severity levels:

• CRITICAL: Security vulnerabilities or bugs that will cause failures
• WARNING: Code smells, potential issues, or maintainability concerns
• SUGGESTION: Style improvements, better patterns, or minor optimizations
• GOOD: Highlight well-written parts (positive feedback matters)

Guidelines

• Be specific — reference line numbers and exact code
• Explain WHY something is an issue, not just WHAT
• Suggest concrete fixes with code examples
• Start with a brief summary before detailed findings
• End with an overall assessment (approve / request changes)