Skip to content
Back to skills

Code Review

ASecurity

Reviews code for quality, best practices, and potential issues. Use when asked to review, audit, or check code for problems.

  • 71 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added February 7, 2026
code-qualitygosqltestingcode-reviewdatabasesecurityperformance

Security analysis

A100/100

Scanned February 10, 2026

npx -y skills add Geeksfino/openskills --skill code-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Code Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Code Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/geeksfino-code-review/badge)](https://www.skillsdirectory.com/skills/geeksfino-code-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: code-review
description: Reviews code for quality, best practices, and potential issues. Use when asked to review, audit, or check code for problems.
allowed-tools: Read, Grep, Glob, LS
context: fork
agent: Explore
---

# Code Review Skill

Perform thorough code reviews following this methodology.

## Review Checklist

### 1. Correctness
- Does the code do what it's supposed to do?
- Are there any logic errors?
- Are edge cases handled?

### 2. Security
- Input validation and sanitization
- Authentication and authorization
- Sensitive data handling
- SQL injection, XSS, and other vulnerabilities

### 3. Performance
- Algorithm complexity
- Unnecessary computations
- Memory leaks or inefficient memory usage
- Database query optimization

### 4. Maintainability
- Code readability and clarity
- Appropriate naming conventions
- Single responsibility principle
- DRY (Don't Repeat Yourself)

### 5. Testing
- Test coverage
- Edge case testing
- Integration tests where appropriate

## Output Format

Structure your review as:

```
## Summary
[One paragraph overview]

## Critical Issues
[Must fix before merge]

## Suggestions
[Nice to have improvements]

## Positive Observations
[What's done well]
```

## Guidelines

- Be constructive, not critical
- Explain *why* something is an issue
- Suggest specific fixes when possible
- Acknowledge good patterns and practices

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…