code-review

Review code changes for correctness, security, performance, and maintainability with severity-tagged fixes.

Updated May 5, 2026
One-click install
npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill code-review-shakhovskiya-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/shakhovskiya-create/shakhoff-claude-marketplace/tree/main/plugins/solo-sdlc/skills/code-review
Command: npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill code-review-shakhovskiya-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, multi-perspective review of code changes to catch correctness, security, performance, and maintainability issues before shipping.

Core Features & Use Cases

  • Four independent lenses (Correctness, Security, Performance, Maintainability) to identify defects and improvement opportunities.
  • Parallel sub-agent execution when available to speed up reviews, with aggregated severity tagging and concrete fixes.
  • Triggered after verification passes or on demand to produce a formal, actionable review report.

Quick Start

Provide the change set after verification to generate a comprehensive, severity-tagged review report detailing issues and recommended fixes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I perform a multi-perspective code review on recent changes?

Multi-perspective code review evaluates change sets across correctness, security, performance, and maintainability lenses to surface concrete fixes. It generates a structured report with severity tags and actionable remediation steps to guide developers before shipping.

What is the best way to catch security and performance issues before shipping code?

To catch security and performance issues before shipping, run a review process that applies independent analysis lenses to the verified change set. This identifies defects and improvement opportunities, producing an aggregated severity-tagged report with recommended fixes.

When should I run a maintainability and correctness review on my codebase?

Run a maintainability and correctness review after verification passes or on demand when you have implemented changes. This triggers formal analysis of the change set to identify potential defects and output actionable remediation steps.

Can I use parallel sub-agent execution to speed up code reviews?

Yes, parallel sub-agent execution can be used to speed up code reviews when available. The process applies multiple analysis lenses concurrently and aggregates the findings into a single severity-tagged report detailing issues and concrete fixes.

Does the code review process require verification to pass before analysis?

Yes, the code review process is designed to be triggered after verification passes. Providing the change set at this stage ensures the review focuses on assessing correctness, security, performance, and maintainability to produce actionable fixes.

What limitations exist when reviewing code changes without aggregated severity tagging?

Reviewing code changes without aggregated severity tagging lacks structured prioritization for identified defects. Applying parallel lenses with severity tags ensures developers receive a formal, actionable report detailing specific issues and concrete remediation steps.