23 lines
842 B
Markdown
23 lines
842 B
Markdown
---
|
|
name: review
|
|
description: "Code review — анализ кода на ошибки, стиль, производительность и безопасность"
|
|
---
|
|
|
|
# Code Review
|
|
|
|
When asked to review code, follow this process:
|
|
|
|
1. **Read the files** mentioned by the user
|
|
2. **Analyze** for:
|
|
- Bugs and logic errors
|
|
- Security vulnerabilities (injection, auth issues, data leaks)
|
|
- Performance problems (N+1 queries, unnecessary allocations, blocking calls)
|
|
- Code style and readability
|
|
- Missing error handling
|
|
3. **Output** a structured review:
|
|
- List issues by severity: critical > warning > suggestion
|
|
- For each issue: file, line, description, fix suggestion
|
|
- End with a summary: "X critical, Y warnings, Z suggestions"
|
|
|
|
Keep feedback actionable and concise. Don't nitpick formatting if there's a linter.
|