Code Reviewing Skill for Claude

by huangjia2019

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.

498 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

1038

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/huangjia2019/claude-code-engineering --skill code-reviewing

The instruction itself

9 sections, as written by the author

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

First, understand what the code is trying to do
Read through the code systematically
Check each item on the checklist
Note any issues found
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

Other skills for the same job

different authors, same section of the catalogue

Receiving Code Review

by ZhanlinCui

×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens

Requesting Code Review

by ZhanlinCui

×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Comprehensive GitHub code review with AI-powered swarm coordination

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

How to use it

Copy the folder

Take huangjia2019/code-reviewing from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.