review-code

Review current git changes for SOLID violations, security risks, and maintainability concerns.

147|31|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/serpro69/claude-toolbox --skill review-code-serpro69
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-code
Source: https://github.com/serpro69/claude-toolbox/tree/main/kodex-plugin/skills/review-code
Command: npx skills add https://github.com/serpro69/claude-toolbox --skill review-code-serpro69

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews are time-consuming and error-prone; this skill provides a structured, expert lens to analyze git changes for SOLID violations, security risks, and maintainability issues.

Core Features & Use Cases

  • Structured review flow that loads profile-specific checklists and assesses architectural concerns.
  • Supports Standard and Isolated review modes with rigorous output including prioritized findings.
  • Use Case: Before merging a diff, obtain a comprehensive, action-ready review highlighting risks and improvements.

Quick Start

Run the review-code skill on your current git diff to generate a structured expert code review.

Frequently Asked Questions about review-code

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

FAQPage Schema
How do I automate a code review for my git diff?

To automate code review for your git diff, run the review-code skill on your current changes. It analyzes git diffs to identify SOLID violations, security risks, and maintainability issues, generating structured findings with severity levels.

What is an isolated review mode for git changes?

An isolated review mode for git changes evaluates the specific diff without the broader context of the entire codebase. This skill supports both standard and isolated modes to apply profile-driven checklists and assess architectural concerns accurately.

Can I check for SOLID violations and security risks before merging a diff?

Yes, you can check for SOLID violations and security risks before merging a diff. This skill performs expert-grade analysis of git changes, applying profile-specific checklists to highlight architectural risks and outputting prioritized findings.

Does static analysis for code review support multiple programming languages?

Static analysis for code review supports multiple programming languages by applying profile-driven checklists. This ensures architectural integrity is assessed consistently across different languages and frameworks during the git diff review process.

How are code review findings prioritized and structured for governance?

Code review findings are prioritized using severity levels from P0 to P3 and include indexing metadata like kk:review-findings. This structured output supports integration and governance by clearly identifying the urgency of each risk.