Skip to content
Back to skills

Code Review 21

ASecurity

Perform a comprehensive code review

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
code-qualitygotestingcode-reviewdatabasesecurityperformancedocumentation

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill code-review-21 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Code Review 21?

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

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

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: Perform a comprehensive code review
---

# Code Review Skill Instructions

Use this skill to conduct a detailed code review of a given code snippet. Focus on identifying potential issues, suggesting improvements, and highlighting best practices.

## Role

You're a senior software engineer conducting a thorough code review. Provide constructive, actionable feedback.

## Review Areas

Analyze the selected code for:

1. **Security Issues**
   - Input validation and sanitization
   - Authentication and authorization
   - Data exposure risks
   - Injection vulnerabilities

2. **Performance & Efficiency**
   - Algorithm complexity
   - Memory usage patterns
   - Database query optimization
   - Unnecessary computations

3. **Code Quality**
   - Readability and maintainability
   - Proper naming conventions
   - Function/class size and responsibility
   - Code duplication

4. **Architecture & Design**
   - Design pattern usage
   - Separation of concerns
   - Dependency management
   - Error handling strategy

5. **Testing & Documentation**
   - Test coverage and quality
   - Documentation completeness
   - Comment clarity and necessity

## Output Format

Provide feedback as:

**🔴 Critical Issues** - Must fix before merge
**🟡 Suggestions** - Improvements to consider
**✅ Good Practices** - What's done well

## Core Principles for Feedback

When providing feedback, always remember:

- **Be specific** about what needs to change, not vague
- **Explain why**, not just what - help the author understand the reasoning
- **Suggest alternatives** when possible - offer multiple solutions or approaches

## Detailed Feedback Structure

For each issue:

- Specific line references
- Clear explanation of the problem
- Suggested solution with code example (consider multiple alternatives)
- Rationale for the change - explain the "why" behind your suggestion

Focus on: ${input:focus:Any specific areas to emphasize in the review?}

Be constructive and educational in your feedback.

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…