Code review

Skill bg-szy/TOP-SKILLS/skills/marketplace/code-review

全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard

Install

npx -y skills add bg-szy/TOP-SKILLS --skill code-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use this skill when user asks to "review code", "check for issues", "analyze code quality", "find bugs", or wants feedback on code implementation.

SKILL.md

2.7 KB, as published. Nobody here has run it

Code Review

Perform thorough code review analyzing quality, potential bugs, security issues, and suggesting improvements.

Parameters

{
  "type": "object",
  "properties": {
    "target": {
      "type": "string",
      "description": "File path, directory, or glob pattern to review"
    },
    "focus": {
      "type": "string",
      "enum": ["general", "security", "performance", "maintainability"],
      "description": "Primary focus area",
      "default": "general"
    }
  },
  "required": ["target"]
}

When to Use

User asks to "review" or "check" code
User wants to find bugs or issues
User asks about code quality
User wants security analysis
User asks for improvement suggestions

Methodology

Phase 1: Context Gathering

Read the target files
Understand the codebase structure
Identify the programming language and framework
Check for related tests and documentation

Phase 2: Analysis

Logic Review: Check for bugs and edge cases
Security Scan: Look for vulnerabilities (injection, auth issues, etc.)
Performance Check: Identify bottlenecks and inefficiencies
Style Review: Check consistency and best practices

Phase 3: Prioritization

Categorize issues by severity (Critical, High, Medium, Low)
Focus on actionable feedback
Provide concrete examples

Phase 4: Output

Provide structured review with:

Summary of findings
Issues list with severity and line numbers
Specific improvement suggestions
Code examples where helpful

Guidelines

Be constructive, not just critical
Provide specific line references
Explain WHY something is an issue
Suggest concrete fixes, not just problems
Acknowledge good patterns when found
Consider the project's existing style

Examples

Example 1: File Review

User Input: "Review src/auth.ts for security issues"

Expected Behavior:

Read the file and understand authentication flow
Check for common security issues (SQL injection, XSS, weak crypto)
Verify input validation and sanitization
Check for proper error handling
Provide prioritized list of findings with fixes

Example 2: Directory Review

User Input: "帮我 review 一下 src/utils/ 目录的代码质量"