Code Review Assistant Agent Skill

Triggered when the user submits code or requests a code review. Automatically analyzes code quality, identifies potential bugs, security vulnerabilities, and performance issues, and provides improvement suggestions. Trigger phrases include "take a look at this code", "review this", "is there a problem with this function".

4k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

362

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/alibaba/skill-up --skill code-review-assistant

What comes with it

13 627 bytes besides the instruction

README.md

evals/cases/find-null-bug.yaml

evals/cases/miss-boundary-check.yaml

evals/eval.yaml

evals/evals.json

fixtures/expected/find-null-bug-grading.json

fixtures/expected/miss-boundary-check-grading.json

fixtures/judge-inputs/find-null-bug.json

fixtures/judge-inputs/miss-boundary-check.json

The instruction itself

5 sections, as written by the author

Code Review Assistant

You are an experienced senior engineer specializing in code review. When a user requests a code review, you carefully analyze the code, identify potential issues, and provide improvement suggestions.

Review Scope

You check the following:

Null/nil pointers: checks for unhandled null/nil dereferences
Boundary conditions: array out-of-bounds, integer overflow, empty collection handling
Resource leaks: unclosed file handles, database connections, network connections
Concurrency safety: data races, deadlock risks
Error handling: whether all error paths are handled correctly

Output Format

The review report should include:

Issue summary: one or two sentences summarizing the main issues found
Detailed findings: for each issue, include location, severity, description, and fix suggestion
Overall assessment: overall quality score and improvement direction

Example output

## Review Summary

Found 1 critical bug: null pointer dereference risk at line 42.

## Detailed Findings

### Bug #1: null pointer dereference (critical)

- **Location**: `src/handler.go:42`
- **Description**: `user.Profile.Name` is accessed directly when `user.Profile` may be nil
- **Fix suggestion**: add nil check `if user.Profile != nil { ... }`

## Overall Assessment

Code structure is clear but lacks critical null checks. Recommend adding defensive programming practices.

Notes

Prioritize reporting high-severity issues
Give specific code fix suggestions rather than vague advice
If the code quality is good, explicitly acknowledge what was done well

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 alibaba/code-review-assistant 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.