One-click install
npx skills add https://github.com/realsigridjin/oh-my-codex --skill code-review-realsigridjin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/realsigridjin/oh-my-codex/tree/main/skills/code-review
Command: npx skills add https://github.com/realsigridjin/oh-my-codex --skill code-review-realsigridjin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify security vulnerabilities, bugs, performance problems, and maintainability issues before code is merged or deployed.

Core Features & Use Cases

  • Comprehensive Analysis: Reviews code changes for security, quality, performance, best practices, and maintainability.
  • Severity-Based Findings: Classifies issues as CRITICAL, HIGH, MEDIUM, or LOW with concrete remediation guidance.
  • Agent-Assisted Review: Delegates deep analysis to a specialized code-reviewer agent and optionally cross-validates findings with Codex.
  • Use Case: Review a pull request before merging to surface injection risks, inefficient algorithms, inadequate error handling, and missing tests with precise file and line references.

Quick Start

Ask the code-review skill to review the current git diff and provide a severity-rated report with file locations, fixes, and an approval recommendation.

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 pull request for security vulnerabilities and maintainability issues?

Reviewing a pull request for security and maintainability issues requires analyzing git diffs to surface injection risks, inefficient algorithms, and inadequate error handling. This process provides severity-rated findings with precise file and line references alongside concrete remediation guidance.

What is static analysis for code changes before deployment?

Static analysis for code changes before deployment identifies security vulnerabilities, bugs, performance problems, and maintainability issues before code is merged. It classifies issues by severity levels ranging from CRITICAL to LOW to help prioritize remediation efforts.

How do I get severity-rated bug detection findings for a git diff?

To get severity-rated bug detection findings for a git diff, you analyze the specified file scope and classify issues as CRITICAL, HIGH, MEDIUM, or LOW. The output includes precise file locations, actionable fixes, and an overall approval recommendation.

Can I use code review automation for refactoring assessments on unfamiliar codebases?

Code review automation applies to refactoring assessments and high-stakes production code across unfamiliar or complex codebases. It evaluates code quality, performance, and best practices to ensure structural changes do not introduce regressions.

Does automated code review work without specifying a file scope or git diff?

Automated code review requires a git diff or a specified file scope to function accurately. Without defining the boundaries of the code changes, the review cannot isolate security vulnerabilities or maintainability issues effectively.