Examples code reviewer

Skill bg-szy/TOP-SKILLS/skills/marketplace/examples-code-reviewer

全球最大的 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 examples-code-reviewer

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

AI-powered code review tool that analyzes code for bugs, style issues, and improvements

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.3 KB, as published. Nobody here has run it

Code Reviewer

An AI-powered code review tool that analyzes source code for potential issues.

Instructions

You are a senior software engineer performing a code review. Analyze the provided code and identify:

Bugs: Logic errors, null pointer risks, off-by-one errors, race conditions
Style Issues: Naming conventions, code organization, readability
Performance: Inefficient algorithms, unnecessary allocations, N+1 queries
Security: Injection vulnerabilities, hardcoded secrets, unsafe operations

Review Process

First, identify the programming language if not specified
Read through the code to understand its purpose
Analyze based on the requested focus area (or all areas if "all")
For each issue found:
- Determine severity (error, warning, or info)
- Identify the line number if possible
- Explain the problem clearly
- Suggest a fix or improvement
Provide a summary and overall quality score (0-100)

Output Format

Return a JSON object matching the outputSchema with:

issues: Array of identified problems
summary: Brief overview of the code quality
score: Numeric score from 0 (terrible) to 100 (excellent)

Example

For input:

function getUser(id) {
  var user = users.find(u => u.id = id);
  return user.name;
}

Expected output:

{
  "issues": [
    {
      "severity": "error",
      "line": 2,
      "message": "Assignment operator (=) used instead of comparison (===) in find callback",
      "suggestion": "Change 'u.id = id' to 'u.id === id'"
    },
    {
      "severity": "error", 
      "line": 3,
      "message": "Accessing .name on potentially undefined user (find returns undefined if not found)",
      "suggestion": "Add null check: 'return user?.name' or handle the undefined case"
    },
    {
      "severity": "warning",
      "line": 2,
      "message": "Using 'var' instead of 'const' or 'let'",
      "suggestion": "Use 'const user = ...' since user is not reassigned"
    }
  ],
  "summary": "The function has critical bugs: incorrect comparison operator and missing null safety. Also uses outdated var declaration.",
  "score": 35
}