code-review

Identify and report code quality and security issues in git diffs.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/glfruit/gorin-skills --skill code-review-glfruit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/glfruit/gorin-skills/tree/main/openclaw/code-review
Command: npx skills add https://github.com/glfruit/gorin-skills --skill code-review-glfruit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the quality and security review of git changes by providing a structured, findings-driven assessment that flags issues and suggests actionable fixes.

Core Features & Use Cases

  • Detect SOLID violations, security risks, race conditions, error-handling gaps, performance regressions, and boundary bugs.
  • Output severity-classified findings (P0–P3) with actionable fixes.
  • Review-first by default; no changes are applied until you explicitly approve.
  • Suitable for pre-merge reviews, PR diffs, and local diffs across multiple languages and projects.

Quick Start

Invoke this skill on your current diff to receive a structured code review before merging.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review a git diff for security and code quality issues before merging?

To review a git diff for security and code quality issues, analyze changes to detect SOLID violations, race conditions, and boundary bugs. This process provides a structured, findings-driven assessment that flags issues with severity-classified, actionable fixes before merging.

What is the best way to check a pull request for SOLID violations and performance regressions?

Checking a pull request for SOLID violations and performance regressions requires a structured code review of the diff. This approach identifies and reports code quality and security issues, categorizing findings by severity from P0 to P3 with suggested actionable fixes.

Does this code review skill apply changes to my local diff automatically?

This code review skill does not apply changes to your local diff automatically. It operates review-first by default, meaning no modifications are applied until you explicitly approve the suggested actionable fixes for the identified code quality and security issues.

Can I use this to find race conditions and error-handling gaps across multiple programming languages?

You can use this to find race conditions and error-handling gaps across multiple programming languages. It performs pre-merge reviews, PR diffs, and local diffs across multiple projects, comprehensively analyzing security, performance, and boundary checks.

How are code review findings prioritized when analyzing a git diff?

Code review findings are prioritized by categorizing them into severity levels from P0 to P3. This classification identifies and reports code quality and security issues in git diffs, delivering actionable findings ranked by criticality for effective triage.

When do I need a structured code review for my git changes?

A structured code review for your git changes is needed during pre-merge reviews, pull requests, or when evaluating local diffs. It streamlines quality and security assessment by flagging issues like SOLID violations, race conditions, and performance regressions with actionable fixes.