skills.rest
Omar-Obando
Omar-ObandoCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Review code changes for correctness, security, and quality issues.

44|9|Updated May 7, 2026
Search Tags:#code review#pull request#clean code#owasp#maintainability#security audit#solid principles
One-click install
npx skills add https://github.com/Omar-Obando/qwen-orchestrator --skill code-review-omar-obando
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Omar-Obando/qwen-orchestrator/tree/main/skills/code-review
Command: npx skills add https://github.com/Omar-Obando/qwen-orchestrator --skill code-review-omar-obando

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you catch correctness, security, and quality issues before they ship by providing a structured, evidence-based code review process aligned with OWASP, SOLID, and Clean Code principles.

Core Features & Use Cases

  • Correctness auditing: Validate edge cases, null/undefined handling, and error-condition behavior.
  • Security-focused review: Check injection risks, authorization, secret leakage, input validation, and dependency vulnerabilities.
  • Quality assessment: Evaluate performance hotspots, maintainability constraints, testing completeness, and architecture boundaries.
  • Common use cases: Pull request reviews, security-oriented quality checks, team coding standards enforcement, and pre-merge risk reduction.

Quick Start

Use the code-review skill to review the changes in your pull request and produce a severity-classified report with evidence and recommendations.

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 security audit on a pull request?▼

Perform a pull request security audit by checking injection risks, authorization, secret leakage, and input validation against an OWASP-aligned checklist to produce a severity-classified markdown report with actionable recommendations.

What is the best way to enforce clean code and SOLID principles during code reviews?▼

Enforce clean code and SOLID principles by evaluating maintainability constraints and architecture boundaries to identify quality issues, yielding an evidence-based markdown report that ensures code changes meet team standards.

How do I check code correctness and handle edge cases before merging?▼

Check code correctness by validating edge cases, null handling, and error-condition behavior to identify correctness issues, yielding a severity-classified report with evidence that reduces pre-merge risk.

Does this code review process work for team coding standard enforcement?▼

Yes, this code review process works for team coding standard enforcement by applying a structured OWASP, SOLID, and Clean Code aligned checklist to identify maintainability and architecture issues across application source code.

What are the limitations of automated code review for security vulnerabilities?▼

Limitations of automated code review for security vulnerabilities include reliance on an OWASP-aligned checklist to identify injection risks and dependency vulnerabilities, yielding a markdown report that may require manual analysis for complex architecture boundaries.

Related Skills

Explore More Software Engineering Skills→
thetangstrthetangstr

pr-report

Analyze pull request code changes and generate structured Markdown or HTML reports.

Community
Advanced
ibalasiteibalasite

land-and-deploy

Merge pull requests, wait for CI, and verify production health via canary checks.

Community
Advanced
nguyenphpnguyenphp
41

lint-and-validate

Run linters, type checkers, and security audits across Node.js and Python projects.

Community
Intermediate
erichowenserichowens
181

security-auditor

Identifies security vulnerabilities in codebases and dependencies across multiple languages.

Community
Advanced