home / Coding / Code Review Skill by @w95

Code Review Skill by @w95

FREE

github stars★ 286updatedFeb 2026repo@w95

$git clone https://github.com/w95/awesome-claude-corporate-skills

The skill is the 08-it-engineering/code-review folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.

about Code Review Skill by @w95

Review code for bugs, security vulnerabilities, performance issues, and maintainability.

our take

Reviews code along four dimensions: security, performance, correctness and maintainability. It triggers on plain requests such as 'review this code' or 'is this code safe?', so it works as a ready-made review checklist for a diff or a whole file.

when to use it

You want a structured second opinion on a pull request
You need security and performance checked in the same pass
You want review comments sorted by what matters most

before you install

An agent review supplements a human reviewer and does not replace one
It only sees the code you give it, so context about intent still has to come from you

what's inside

The original SKILL.md is organised into these sections:

Review Dimensions
Security
Performance
Correctness
Maintainability
Output Format

source and license

Written and maintained by @w95. It is published under the MIT license, which allows reuse with attribution. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.

View the full SKILL.md on GitHub ↗

Read the opening of the original SKILL.md

# Code Review

Structured code review covering security, performance, correctness, and maintainability. Works on diffs, PRs, files, or pasted code snippets.

## Review Dimensions

### Security
- SQL injection, XSS, CSRF
- Authentication and authorization flaws
- Secrets or credentials in code
- Insecure deserialization
- Path traversal
- SSRF

### Performance
- N+1 queries
- Unnecessary memory allocations
- Algorithmic complexity (O(n²) in hot paths)
- Missing database indexes
- Unbounded queries or loops
- Resource leaks

### Correctness
- Edge cases (empty input, null, overflow)
- Race conditions and concurrency issues
- Error handling and propagation
- Off-by-one errors
- Type safety

### Maintainability
- Naming clarity
- Single responsibility
- Duplication
- Test coverage
- Documentation for non-obvious logic

## Output Format
…

Excerpt only, quoted from the author's repository. Open the repository for the complete file.

↓ download .zip