code-reviewer

Analyze code diffs to identify bugs, security vulnerabilities, and code smells.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/Design-System-ET/genexus-dev-opencode --skill code-reviewer-design-system-et
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/Design-System-ET/genexus-dev-opencode/tree/main/skills/code-reviewer
Command: npx skills add https://github.com/Design-System-ET/genexus-dev-opencode --skill code-reviewer-design-system-et

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the challenge of maintaining high code quality, security, and architectural integrity during the development lifecycle by providing automated, structured, and actionable feedback on pull requests.

Core Features & Use Cases

  • Comprehensive Analysis: Identifies bugs, security vulnerabilities (SQL injection, XSS), code smells, and N+1 query patterns.
  • Actionable Reporting: Generates a prioritized report categorized by critical, major, and minor issues with specific remediation steps.
  • Use Case: Use this skill when conducting a pull request review to ensure that new code adheres to SOLID principles, maintains test coverage, and avoids common security pitfalls before merging into the main branch.

Quick Start

Invoke the code-reviewer skill to analyze the current pull request and generate a structured quality report.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I review a pull request for security vulnerabilities and code smells?

Reviewing a pull request involves analyzing code diffs to identify security vulnerabilities, code smells, and architectural concerns. This generates a prioritized, actionable report categorized by severity with specific remediation steps based on industry best practices.

What is the best way to audit code quality before merging into the main branch?

Auditing code quality before merging requires analyzing files to ensure adherence to SOLID principles and test coverage. It identifies bugs and architectural concerns, generating an actionable quality report that prevents common security pitfalls from entering the main branch.

Does this code review approach work across various programming languages?

Yes, this code review approach applies to pull request reviews, code quality audits, and refactoring tasks across various programming languages. It analyzes code diffs and files to identify bugs, security vulnerabilities, and architectural concerns regardless of the specific language used.

How do I get actionable feedback for refactoring tasks based on static analysis?

Getting actionable feedback for refactoring tasks involves applying static analysis to code files to detect architectural concerns and code smells. This yields a prioritized report with specific remediation steps based on industry-standard best practices.

When do I need a structured code review for my development lifecycle?

You need a structured code review when maintaining high code quality, security, and architectural integrity during the development lifecycle. It provides automated, structured feedback on pull requests to ensure new code avoids common security pitfalls.