code-review

Generate severity-rated code reviews with file:line findings and approval decisions.

2|Updated May 11, 2026
One-click install
npx skills add https://github.com/xz1220/oh-my-kimi --skill code-review-xz1220
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/xz1220/oh-my-kimi/tree/main/skills/code-review
Command: npx skills add https://github.com/xz1220/oh-my-kimi --skill code-review-xz1220

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of missing quality, security, and maintainability issues during development by producing a structured, evidence-backed review with clear pass/fail guidance.

Core Features & Use Cases

  • Severity-rated findings: Categorizes issues into CRITICAL, HIGH, MEDIUM, and LOW with rationale.
  • Dual-lane evaluation: Runs a code-quality/security lane and an architecture devil’s-advocate lane in parallel, then synthesizes results into a single actionable outcome.
  • Actionable recommendations: Provides file:line locations, concrete fixes, and an approval gate decision (APPROVE / REQUEST CHANGES / COMMENT).

Quick Start

Ask for a code review by saying: “/skill:code-review Review the changes in this PR for security, quality, and maintainability.”

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I run a severity-rated code review on a pull request?

To run a severity-rated code review, trigger the skill with a pull request diff. It evaluates changes in parallel lanes, categorizing issues into CRITICAL, HIGH, MEDIUM, and LOW, then synthesizes an approval gate decision.

What is dual-lane evaluation in a code review?

Dual-lane evaluation runs a code-quality and security lane alongside an architecture devil’s-advocate lane in parallel. This mechanism identifies both immediate vulnerabilities and broader design tradeoffs before merging.

Can I use this code review for pre-merge security checks on backend codebases?

Yes, you can use this for pre-merge security checks across typical web and backend codebases. It requires diff-scoped evaluation to produce evidence-backed findings with file:line locations.

How do I get actionable remediation steps for maintainability issues?

To get actionable remediation steps for maintainability issues, submit your proposed code changes for review. The process provides concrete fixes and an approval gate decision of APPROVE, REQUEST CHANGES, or COMMENT.

What's the best way to check architecture tradeoffs before merging code?

The best way to check architecture tradeoffs is using a devil’s-advocate evaluation lane. It runs parallel to quality checks, synthesizing deterministic findings into a single actionable outcome for your pull request.