SkillHub ClubRun DevOpsFull StackSecurity

code-review

Review Python code for quality, security, and best practices

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars

489

Hot score

Updated

March 20, 2026

Overall rating

C3.6

Composite score

3.6

Best-practice grade

B84.0

Install command

npx @skill-hub/cli install vstorm-co-pydantic-deepagents-code-review

codereviewpythonquality

Repository

vstorm-co/pydantic-deepagents

Skill path: examples/skills/code-review

Review Python code for quality, security, and best practices

Open repository

Best for

Primary workflow: Run DevOps.

Technical facets: Full Stack, Security.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: vstorm-co.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

Install code-review into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
Review https://github.com/vstorm-co/pydantic-deepagents before adding code-review to shared team environments
Use code-review for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
name: code-review
description: Review Python code for quality, security, and best practices
version: 1.0.0
tags:
  - code
  - review
  - python
  - quality
author: pydantic-deep
---

# 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.