Skip to content
Back to skills

Code Review

ASecurity

Reviews code diffs and files for security vulnerabilities (OWASP Top 10), error handling, complexity, naming conventions, and performance issues. Use when the user asks to review a PR, pull request, diff, merge request, or code changes.

  • 2,921 stars
  • 0 votes
  • 0 copies
  • 8 views
  • Added May 26, 2026
code-qualitypythongosqlcode-reviewgitsecurityperformance

Works with

  • cursor

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add open-gitagent/opengap --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/open-gitagent-code-review/badge)](https://www.skillsdirectory.com/skills/open-gitagent-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 diffs and files for security vulnerabilities (OWASP Top 10), error handling, complexity, naming conventions, and performance issues. Use when the user asks to review a PR, pull request, diff, merge request, or code changes."
license: MIT
allowed-tools: lint-check complexity-analysis
metadata:
  author: gitagent-examples
  version: "1.0.0"
  category: developer-tools
---

# Code Review

## Instructions
When reviewing code:
1. Read the full diff or file provided
2. Check for security vulnerabilities (OWASP Top 10)
3. Evaluate error handling completeness
4. Assess code complexity and readability
5. Verify naming conventions and code style
6. Look for performance issues
7. Check for proper input validation

## Output Format
```
## Review Summary
[1-2 sentence overview]

## Findings

### CRITICAL
- [Finding with line reference and fix]

### WARNING
- [Finding with line reference and fix]

### SUGGESTION
- [Finding with line reference and fix]

## What's Done Well
- [Positive observations]
```

### Example Finding

```
### CRITICAL
- **Line 42**: SQL injection vulnerability — user input concatenated directly into query string.
  Fix: Use parameterized queries instead of string concatenation.
  ```python
  # Before (vulnerable)
  cursor.execute(f"SELECT * FROM users WHERE id = {user_id}")
  # After (safe)
  cursor.execute("SELECT * FROM users WHERE id = %s", (user_id,))
  ```
```

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…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.