review

Analyze code changes for security, performance, quality, and architecture issues.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/manastalukdar/claude-devstudio --skill review-manastalukdar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/manastalukdar/claude-devstudio/tree/main/skills/review
Command: npx skills add https://github.com/manastalukdar/claude-devstudio --skill review-manastalukdar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code for security vulnerabilities, performance bottlenecks, quality issues, and architectural concerns, saving significant developer time and improving code reliability.

Core Features & Use Cases

  • Multi-Agent Analysis: Employs specialized sub-agents for security, performance, quality, and architecture.
  • Token Optimization: Aggressively reduces token usage through techniques like git diff scoping, grep-before-read, and progressive disclosure.
  • Caching: Stores previous review results to speed up subsequent analyses of unchanged files.
  • Use Case: Before merging a pull request, run /review to get a quick assessment of potential issues in the changed files, ensuring code quality and security standards are met.

Quick Start

Run the review skill to analyze the code changes in the current branch.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review for security vulnerabilities and performance bottlenecks?

Automated code review for security and performance is achieved by running a multi-agent analysis that scans changed files using shell scripting and grep patterns. This process identifies security vulnerabilities, performance bottlenecks, and architectural concerns automatically.

Can I scope automated code analysis to only changed files in my current branch?

Yes, you can scope automated code analysis to only changed files in your current branch. The review mechanism defaults to analyzing git diff output for modified files, while also offering options for full codebase reviews.

What is the best way to reduce token usage during a full codebase architecture review?

The best way to reduce token usage during a full codebase architecture review is to use techniques like git diff scoping, grep-before-read, and progressive disclosure. Caching previous results also speeds up subsequent analyses.

Does this automated code quality analysis require any external dependencies?

No, this automated code quality analysis requires no external dependencies. It implements multi-agent security, performance, and architecture checks entirely using optimized shell scripts and internal components.

How does caching work for automated security scans on unchanged files?

Caching for automated security scans stores previous review results locally to speed up subsequent analyses. By retaining these results, the system skips reprocessing unchanged files, improving token efficiency.