code-review

Analyze diffs and generate structured code-review reports aligned with the 6 Decision Principles.

2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Wilder1222/superomni --skill code-review-wilder1222
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Wilder1222/superomni/tree/main/skills/code-review
Command: npx skills add https://github.com/Wilder1222/superomni --skill code-review-wilder1222

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canonical review workflow for code quality, providing structured, actionable feedback that moves PRs forward without blocking momentum.

Core Features & Use Cases

  • Canonical review workflow across giving, receiving, and security-focused reviews, with a unified rubric based on the 6 Decision Principles.
  • Provides stepwise layers: Correctness, Security, Tests, Code Quality, Blast Radius, and Architecture considerations.
  • Dispatches the code-review agent with diffs and relevant source files to generate a comprehensive report and integrate results into the project.

Quick Start

Run the code-review skill against your PR by providing the diffs and repository context.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I generate actionable code review insights from a pull request diff?

To generate actionable code review insights from a pull request diff, analyze the changes against repository context to surface feedback on correctness, security, tests, performance, and readability. This approach produces a structured, auditable review artifact anchored to the project context.

What is the best way to structure security-focused code reviews for internal engineering workflows?

A structured security-focused code review applies a unified rubric across stepwise layers, evaluating blast radius and architecture considerations alongside correctness. This canonical workflow ensures comprehensive security analysis anchored to the 6 Decision Principles.

Can I use a single rubric for both giving and receiving code feedback across different PRs?

Yes, you can apply a unified rubric based on the 6 Decision Principles to standardize both giving and receiving code feedback across pull requests. This canonical review workflow generates a comprehensive, auditable report for consistent quality evaluation.

How does analyzing relevant source files improve code quality feedback during a PR review?

Analyzing relevant source files alongside diffs improves code quality feedback by anchoring insights to the actual project context. This dispatches a comprehensive review across correctness, tests, performance, and architecture to generate an auditable report.

What dimensions should a comprehensive code review cover to ensure software engineering quality?

A comprehensive code review for software engineering quality should cover stepwise layers including Correctness, Security, Tests, Code Quality, Blast Radius, and Architecture considerations. These dimensions ensure structured feedback aligned with the 6 Decision Principles.