Review

This gives you a structured code review workflow that treats every git diff like a PR review, complete with severity classifications (S0 through S3), must-fix checklists, and an approve/reject verdict. It reads the full modified files for context, not just the diff hunks, and checks against your project docs before flagging style issues. The four-tier severity system is practical: S0/S1 block merges, S2/S3 are suggestions. What I like is that it enforces concrete output: every finding needs a location, impact statement, and fix suggestion, plus a confidence level. It's opinionated about structure but flexible enough to adapt to your project standards. Good for teams that want consistent review quality without the ceremony of opening an actual PR.

skills.sh installs: 210
GitHub stars: 48
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add buiducnhat/agent-skills --skill review --agent claude-code

Installs into .claude/skills of the current project.

Files

Review

Overview

Use this skill to review uncommitted changes in the current git workspace.
Focus on correctness, safety, maintainability, and alignment with project standards.

The review must produce:

A concise summary of what changed
Prioritized findings with severity labels
Actionable fix suggestions
A final verdict (Approve or Request Changes)

Workflow

Step 1: Gather Context

Inspect current changes:
- git diff
- git diff --cached (if staged changes exist)
Read the full modified files (not only the diff hunks) to understand surrounding logic and architecture.
Load only the project context relevant to the changed files before judging style/patterns:
- If docs/SUMMARY.md exists, read it first.
- Load only task-relevant detail docs.
- Prioritize Code Standard docs for implementation conventions.
- If docs conflict with code or user intent, use the available input/question tool before broad changes.
Run relevant quality checks for touched areas (lint/type/tests when practical).