kimi-code-review

Review code diffs with the Kimi Code CLI and relay severity-marked findings.

Updated Aug 27, 2026

Search Tags:#code review #code changes #git diff #second opinion #diff review #moonshot #kimi code review

Ready to run

npx skills add https://github.com/dongzhuoyao/deepresearch --skill kimi-code-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kimi-code-review
Source: https://github.com/dongzhuoyao/deepresearch/tree/main/.codex/skills/kimi-code-review
Command: npx skills add https://github.com/dongzhuoyao/deepresearch --skill kimi-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the need to rely solely on Codex's native code reviewer by letting you get an independent, second-opinion review of your code changes directly from Kimi (Moonshot), ideal for when you want a fresh perspective on diffs, commits, or working tree changes.

Core Features & Use Cases

Flexible Review Scope: Supports reviewing current branch diffs against a base branch, uncommitted working tree changes, specific commits, or custom diff files.
Custom Review Focus: Lets you pass custom instructions to Kimi to focus on specific areas like security, data loss risks, or performance.
Use Case: Use this Skill when you want a second opinion on a pull request diff, or need Kimi to review uncommitted changes before you push code.

Quick Start

Use the kimi-code-review skill to get a Kimi review of your current branch's code changes against the main branch.

Frequently Asked Questions about kimi-code-review

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

FAQPage Schema

How do I get a second opinion code review on my git diff?▼

You can get a second opinion code review by routing your git diff to an independent reviewer like Kimi, which analyzes current branch changes, uncommitted working tree updates, or specific commits against a configured base branch.

What is the best way to review uncommitted working tree changes?▼

The best way to review uncommitted working tree changes is to use an independent review tool that captures diffs without truncation, ensuring complete feedback on your code before you push.

Can I focus a code review on specific areas like security or performance?▼

Yes, you can focus a code review on security or performance by passing custom instructions to the reviewer, directing the analysis toward data loss risks or other specific areas of concern within the diff.

Does this code review approach support custom diff files?▼

Yes, this independent code review approach supports custom diff files, allowing you to review specific commits, current branch diffs, or manually provided diff files against a base branch without truncating the input.

Why does my code review fail when the Kimi CLI is not available?▼

Your code review fails without the Kimi CLI because the workflow validates its availability and enforces a read-only process with no silent fallbacks to native reviewers, ensuring an independent second opinion.