code-review · vstorm-co — Claude Code skill for code reviews
code-review is a Claude Code skill that checks code for bugs, security issues, style, and performance problems. Ask for a review to run it.
MIT ★ 1,125 updated 2026-10-27
npx skills add vstorm-co/pydantic-deepagents --skill code-review -a claude-codeWhat code-review does
code-review reviews code across correctness, security, performance, maintainability, and testing. It looks for logic errors and edge cases, unsafe input handling, inefficient loops or database queries, dead code, and gaps in test coverage.
Each finding includes a file and line, its category, a description, and a suggested fix. Findings are labeled critical, warning, or suggestion. The checklist also flags missing type annotations and functions longer than 30 lines for splitting.
What it helps with
- catch logic errors and mishandled exceptions
- spot SQL injection and other security flaws
- find redundant loops and database queries
- check whether new code paths have test coverage
- group review findings by location and severity
Example prompts for the agent
- Review these changes for bugs, security risks, and performance issues.
- Check this code for dead code, missing tests, and exception-handling problems.
- List review findings with the file, line, category, and a suggested fix.
How to install code-review
1Skills CLI (Vercel)
npx skills add vstorm-co/pydantic-deepagents --skill code-review -a claude-code2Manually: put the files in place
~/.claude/skills/code-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/code-review/
1Skills CLI (Vercel)
npx skills add vstorm-co/pydantic-deepagents --skill code-review -a codex2Manually: put the files in place
.agents/skills/code-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add vstorm-co/pydantic-deepagents --skill code-review -a cursor2Manually: put the files in place
.cursor/skills/code-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install vstorm-co/pydantic-deepagents apps/cli/skills/code-review2Manually: put the files in place
.github/skills/code-review/SKILL.md1Skills CLI (Vercel)
npx skills add vstorm-co/pydantic-deepagents --skill code-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/vstorm-co/pydantic-deepagents --path apps/cli/skills/code-reviewManually: put the files in place
.devin/skills/code-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about code-review
How do I install code-review in Claude Code?
Run npx skills add vstorm-co/pydantic-deepagents --skill code-review -a claude-code. The skill file is at ~/.claude/skills/code-review/SKILL.md.
What does code-review do?
It checks code for correctness, security and performance issues, maintainability, and test coverage. Each finding includes its location, category, and a suggested fix.
How are code-review findings formatted?
Each finding gives a file and line, category, description, and suggested fix. Its severity is marked critical, warning, or suggestion.
Source text
SKILL.md · MIT
--- name: code-review description: "Systematic code review for bugs, security, style, and performance" tags: [code-quality, review] version: "1.0.0" --- # Code Review Perform a systematic code review covering these categories: ## Review Checklist ### 1. Correctness - Logic errors, off-by-one, null/None handling - Edge cases: empty inputs, large inputs, concurrent access - Error handling: are exceptions caught and handled properly? ### 2. Security - Input validation and sanitization - SQL injection, XSS, command injection - Secrets in code, hardcoded credentials - Authentication and authorization checks ### 3. Performance - Unnecessary loops, N+1 queries - Missing indexes for database queries - Large memory allocations, unbounded collections - Blocking calls in async code ### 4. Style & Maintainability - Naming clarity (variables, functions, classes) - Function length — split if >30 lines - Dead code, commented-out code - Missing type annotations ### 5. Testing - Are new code paths covered by tests? - Are edge cases tested? - Are error paths tested? ## Output Format For each issue found: - **File:line** — category — description — suggested fix - Severity: critical / warning / suggestion
© vstorm-co · MIT · vstorm-co/pydantic-deepagents
Similar skills
All skills for Code review and refactoring →code-review by other authors comes first.