# Review

> Review code for issues, best practices, and improvements. Use when the user asks for a code review, wants feedback on their code, or asks you to check their implementation. Use when this capability is needed.

- Skill: `tomevault-io/review-30` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/review-30`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/review-30/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/review-30

---

# Review Skill

Perform code review focusing on quality, correctness, and maintainability.

## Review Checklist

### Correctness
- Logic errors or edge cases
- Error handling coverage
- Type safety and null checks

### Code Quality (SOLID + Clean Code)
- **Single Responsibility**: One reason to change per class/function
- **Open/Closed**: Open for extension, closed for modification
- **Liskov Substitution**: Subtypes substitutable for base types
- **Interface Segregation**: Specific interfaces over general ones
- **Dependency Inversion**: Depend on abstractions
- DRY, YAGNI, meaningful names, Boy Scout Rule
- Functions: Small (<20 lines), do one thing, few args (0-2)
- No side effects, appropriate abstraction level

### Style Compliance
- Type hints on all functions/methods
- Google-style docstrings
- Absolute imports only
- Line length under 120 chars

### Testing
- Tests cover new functionality
- Tests verify behavior, not implementation
- Edge cases tested
- No flaky tests

### Security
- No hardcoded secrets
- Input validation at boundaries
- Safe handling of user data

## Process

1. Read the code to understand its purpose
2. Run through the review checklist
3. Identify issues by category:
   - **Critical**: Bugs, security issues
   - **Major**: Design problems, missing tests
   - **Minor**: Style, naming, documentation
4. Provide actionable feedback with specific suggestions
5. Note positive aspects of the code

## Output Format

```markdown
## Code Review

### Summary
Brief overview of the code's purpose and quality.

### Critical Issues
- Issue description and location
- Suggested fix

### Suggestions
- Improvement opportunities
- Alternative approaches

### Positive Notes
- Well-done aspects
```

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/oedokumaci) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-11 -->