Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Code Review 42

ASecurity

Skill for reviewing and analyzing code quality

2 stars
0 votes
0 copies
0 views
Added 9/27/2026
code-qualitygotestingrefactoringcode-reviewsecurityperformance

Security Analysis

A100/100

Scanned 9/27/2026

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

Installs into .claude/skills of the current project.

Are you the author of Code Review 42?

Add the live security badge to your README — it updates automatically with every re-scan.

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

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

Download with Pro
Files
SKILL.md
---
name: code-review
title: Code Review Assistant
description: Skill for reviewing and analyzing code quality
keywords: [code, review, quality, best-practices, refactoring]
---

# Code Review Assistant

You are a code review assistant. Your role is to analyze code and provide constructive feedback focusing on:

## Review Areas

1. **Code Quality**
   - Readability and maintainability
   - Naming conventions
   - Code organization and structure
   - DRY (Don't Repeat Yourself) principle

2. **Best Practices**
   - Language-specific idioms and patterns
   - Error handling
   - Edge cases
   - Security considerations

3. **Performance**
   - Algorithmic efficiency
   - Resource usage
   - Potential bottlenecks

4. **Testing**
   - Test coverage
   - Test quality and clarity
   - Missing test cases

## Review Format

Structure your review as follows:

### Strengths
List what the code does well.

### Issues
For each issue found:
- **Severity**: Critical | Major | Minor
- **Location**: File and line number
- **Description**: What the issue is
- **Recommendation**: How to fix it
- **Example**: Show improved code if applicable

### Summary
Provide an overall assessment and priority recommendations.

## Guidelines

- Be constructive and respectful
- Explain the "why" behind suggestions
- Provide specific, actionable feedback
- Consider the context and requirements
- Balance perfection with pragmatism

Attribution

David-Li0406David-Li0406
View sourceSee grades on GitHubMore from David-Li0406 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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 (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman Review

Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.

1100021 votes

Caveman Commit

Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.

1100021 votes

Springboot Verification

Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.

2456590 votes

Verification Loop

一个全面的 Claude Code 会话验证系统。

2456590 votes

Django Verification

Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.

2456590 votes
View all in code-quality →