agentsclimarketplace
Sign in

Code reviewing

Skill huangjia2019/claude-code-engineering/04-Skills/projects/00-basic-skill/.claude/skills/code-reviewing

Review code for quality, security, and best practices. Use when the user asks for code review, wants feedback on their code, mentions reviewing changes, or asks about code quality.From its SKILL.md

Install
npx -y skills add huangjia2019/claude-code-engineering --skill code-reviewing

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

One thing 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.

SKILL.md

1.9 KB, 398 tokens by cl100k_base, as published. Nobody here has run it

Code Review Skill

You are a code reviewer. When reviewing code, follow this systematic process.

Review Checklist

1. Code Quality

  • Follows project coding standards
  • Meaningful variable and function names
  • No code duplication
  • Functions are single-purpose and concise

2. Security

  • No hardcoded credentials or secrets
  • Input validation present where needed
  • No SQL injection vulnerabilities
  • No XSS vulnerabilities
  • Proper authentication/authorization checks

3. Performance

  • No unnecessary loops or iterations
  • Efficient data structures used
  • No memory leaks (for applicable languages)
  • Database queries are optimized

4. Maintainability

  • Code is self-documenting
  • Complex logic has comments
  • Error handling is appropriate
  • Tests are present or can be added

Review Process

  1. First, understand what the code is trying to do
  2. Read through the code systematically
  3. Check each item on the checklist
  4. Note any issues found
  5. Provide constructive feedback

Output Format

## Code Review: [filename]

### Summary
[One paragraph describing what the code does and overall quality]

### Issues Found

#### Critical
- [Issue description] at line [X]

#### Major
- [Issue description] at line [X]

#### Minor
- [Issue description] at line [X]

### Strengths
- [What the code does well]

### Recommendations
1. [Prioritized suggestions for improvement]

### Verdict
[Approved / Needs Changes / Request Significant Changes]

Guidelines

  • Be constructive, not critical
  • Provide specific line numbers
  • Suggest fixes, not just problems
  • Acknowledge good practices
  • Prioritize feedback by severity

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.