Coding

Perform a comprehensive code review covering security, performance, code quality, and adherence to best practices, then deliver prioritized, actionable improvement recommendations with clear explanations.

REVIEW METHODOLOGY:

1. Security Analysis
   - Identify injection vulnerabilities (SQL, XSS, command injection, path traversal)
   - Check for hardcoded secrets, credentials, or API keys
   - Evaluate input validation and sanitization completeness
   - Assess authentication and authorization logic for flaws
   - Flag unsafe deserialization, insecure cryptographic usage, or exposed sensitive data
   - Check for dependency vulnerabilities or outdated library patterns

2. Performance Evaluation
   - Identify unnecessary computations, redundant loops, or O(n^2+) operations that could be optimized
   - Check for memory leaks, unbounded growth, or excessive allocations
   - Evaluate database query efficiency (N+1 queries, missing indexes, full table scans)
   - Assess caching opportunities and unnecessary I/O operations
   - Flag blocking calls in async contexts or missing concurrency controls

3. Code Quality and Style
   - Evaluate naming conventions (variables, functions, classes) for clarity and consistency
   - Assess function/method length and single-responsibility adherence
   - Check for code duplication that should be abstracted
   - Review error handling completeness and consistency
   - Evaluate comment quality: missing where needed, excessive where code should be self-documenting
   - Verify consistent formatting and idiomatic patterns for the language

4. Best Practices and Architecture
   - Assess SOLID principles adherence where applicable
   - Check for proper separation of concerns
   - Evaluate testability of the code structure
   - Identify missing type hints, null checks, or defensive programming gaps
   - Flag anti-patterns specific to the programming language or framework

OUTPUT CONSTRAINTS:
- Categorize every finding as CRITICAL, WARNING, or SUGGESTION
- For each finding: state the problem, explain WHY it matters, and provide a concrete code fix
- Provide a summary scorecard at the end (Security / Performance / Quality / Best Practices each rated Low/Medium/High concern)
- If the code is solid in a category, say so briefly rather than inventing issues
- Prioritize findings by impact: security risks first, then correctness bugs, then performance, then style

FORMAT:
## Review Summary
[1-2 sentence overall assessment]

## Findings

### CRITICAL
[numbered list with code snippets]

### WARNING
[numbered list with code snippets]

### SUGGESTION
[numbered list with code snippets]

## Scorecard
| Category | Rating | Notes |
|----------|--------|-------|

## Refactored Code (if applicable)
[Full corrected version if changes are substantial]

---

MY INFO:

Programming Language: (required)

Code to Review: (required)

Additional Context (what this code does, where it runs): (optional)

Specific Concerns (anything you already suspect): (optional)