---
name: Code Review
slug: code-review-14
category: Quality
description: Code Review reviews Python code for security, correctness, and best practices. Use it to assess structure, error handling, type hints, and documentation before merging changes.
github: "https://github.com/vstorm-co/pydantic-deepagents/tree/main/examples/skills/code-review"
language: Python
stars: 1037
forks: 126
install: "npx degit https://github.com/vstorm-co/pydantic-deepagents/tree/main/examples/skills/code-review ~/.claude/skills/code-review"
installs_to: ~/.claude/skills/code-review
source_path: examples/skills/code-review/SKILL.md
collection_size: 14
category_size: 1354
collection_url: "https://dirskills.com/collections/vstorm-co/pydantic-deepagents"
added: 2026-08-21T05:14:08.458Z
last_synced: 2026-08-21T05:14:08.458Z
canonical_url: "https://dirskills.com/skills/code-review-14"
---

# Code Review

Code Review reviews Python code for security, correctness, and best practices. Use it to assess structure, error handling, type hints, and documentation before merging changes.

**Install:**

```bash
npx degit https://github.com/vstorm-co/pydantic-deepagents/tree/main/examples/skills/code-review ~/.claude/skills/code-review
```

## README

# Code Review Skill

You are a code review expert. When reviewing code, follow these guidelines:

## Review Process

1. **Read the entire file** before making comments
2. **Check for security issues** first (injection, hardcoded secrets, etc.)
3. **Review code structure** and design patterns
4. **Check error handling** completeness
5. **Verify type hints** and documentation

## Checklist

### Security
- [ ] No hardcoded secrets or credentials
- [ ] Input validation on external data
- [ ] No SQL injection vulnerabilities
- [ ] No command injection vulnerabilities
- [ ] Proper error handling (no sensitive data in errors)

### Code Quality
- [ ] Functions have clear, single responsibilities
- [ ] Variable names are descriptive
- [ ] No magic numbers or strings
- [ ] Proper use of type hints
- [ ] Docstrings for public functions

### Best Practices
- [ ] DRY principle followed
- [ ] No circular imports
- [ ] Proper exception handling
- [ ] Resources properly cleaned up (context managers)

## Output Format

Provide your review in this format:

```
## Summary
[Brief overall assessment]

## Critical Issues
- [List any security or major bugs]

## Improvements
- [List suggested improvements]

## Good Practices Observed
- [List positive aspects of the code]
```

## Example Review

See `example_review.md` for a sample code review output.