smart-review

Identify code changes from diffs, PRs, or branches and run parallel security, performance, and quality reviews.

1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/anshul-garg27/claude-enhancement-suite --skill smart-review-anshul-garg27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smart-review
Source: https://github.com/anshul-garg27/claude-enhancement-suite/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/anshul-garg27/claude-enhancement-suite --skill smart-review-anshul-garg27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep code reviews are hard to scale across security, performance, and architecture, leading to blind spots and inconsistent quality.

Core Features & Use Cases

  • Three parallel review lenses (security, performance, code quality) that produce a consolidated, actionable report.
  • Context-aware analysis of diffs, PRs, and branch changes to surface risk areas early.
  • Guided remediation recommendations and structured findings that map to actionable fixes.

Quick Start

Run a three-lens review by providing the target changes (PR number, branch name, or uncommitted changes).

Frequently Asked Questions about smart-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code reviews for security, performance, and architecture?

Automate code reviews by running parallel subagents that analyze git diffs or pull requests for security, performance, and code quality, producing a consolidated report with actionable remediation recommendations.

What is the best way to review a GitHub pull request for code quality and security?

Review a GitHub pull request by passing the PR number to fetch the diff and context via gh CLI, which then triggers parallel security, performance, and code quality reviews to surface risk areas early.

Can I review unstaged git changes for performance and security issues?

Yes, you can review unstaged changes by providing no arguments; the system automatically uses git diff for unstaged changes and git diff --cached for staged changes to perform the three-lens review.

How do I analyze a branch diff against main for code quality?

Analyze a branch diff by providing the branch name, which triggers a git diff main...{branch} command to identify changed files and languages before spawning the parallel code quality, security, and performance review subagents.

Does deep code review work if there are no changes in the git diff?

No, if the git diff is empty, the code review process reports that there are no changes to review and stops, preventing unnecessary execution of the security, performance, and quality subagents.