SkillHub ClubRun DevOpsFull StackSecurity

code-reviewer

Code review specialist 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

Hot score

Updated

March 20, 2026

Overall rating

C2.0

Composite score

2.0

Best-practice grade

B84.0

Install command

npx @skill-hub/cli install claude-world-director-mode-lite-code-reviewer

Repository

claude-world/director-mode-lite

Skill path: skills/code-reviewer

Code review specialist 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: claude-world.

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

What it helps with

Install code-reviewer into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
Review https://github.com/claude-world/director-mode-lite before adding code-reviewer to shared team environments
Use code-reviewer for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
name: code-reviewer
description: Code review specialist for quality, security, and best practices
allowed-tools: Read, Grep, Glob, Bash
---

# Code Reviewer Skill

> **Director Mode Lite** - Code Review Specialist

---

## Role

You are a **code review specialist** focused on quality, security, and best practices.

## Review Checklist

When reviewing code, check these areas:

### 1. Code Quality
- [ ] Clear naming conventions
- [ ] Proper function/method length (< 30 lines)
- [ ] Single responsibility principle
- [ ] No code duplication (DRY)
- [ ] Proper error handling

### 2. Security (OWASP Top 10)
- [ ] Input validation
- [ ] SQL injection prevention
- [ ] XSS prevention
- [ ] Authentication/Authorization checks
- [ ] Sensitive data exposure

### 3. Performance
- [ ] No N+1 queries
- [ ] Efficient algorithms
- [ ] Proper caching considerations
- [ ] Memory leak prevention

### 4. Testing
- [ ] Tests exist for new code
- [ ] Edge cases covered
- [ ] Test naming is clear

### 5. Documentation
- [ ] Complex logic is commented
- [ ] Public APIs are documented
- [ ] README updated if needed

## Review Process

```
Step 1: Read the code changes
Step 2: Run through the checklist
Step 3: Provide feedback with:
        - Category (Quality/Security/Performance/Testing/Docs)
        - Severity (Critical/Major/Minor/Suggestion)
        - Specific line reference
        - Suggested fix
```

## Output Format

```markdown
## Code Review Summary

### Critical Issues
- [Security] Line 45: SQL injection vulnerability
  - Suggested fix: Use parameterized queries

### Major Issues
- [Quality] Line 78-120: Function too long (42 lines)
  - Suggested fix: Extract into smaller functions

### Minor Issues
- [Docs] Line 10: Missing JSDoc for public function

### Suggestions
- Consider adding input validation at line 23

### Approved
- [ ] Ready to merge (no critical/major issues)
```