Agent Skills › MoonshotAI/kimi-code › review-pr

review-pr

GitHub

用于审查 Pull Request，通过获取 PR 元数据和代码 Diff，对照模板结构评估需求、Bug、代码变更等部分的有效性，并生成中文结构化审查总结。

.agents/skills/review-pr/SKILL.md MoonshotAI/kimi-code

Trigger Scenarios

审查拉取请求评估代码变更合理性

Install

npx skills add MoonshotAI/kimi-code --skill review-pr -g -y

More Options

Non-standard path

npx skills add https://github.com/MoonshotAI/kimi-code/tree/main/.agents/skills/review-pr -g -y

Use without installing

npx skills use MoonshotAI/kimi-code@review-pr

指定 Agent (Claude Code)

npx skills add MoonshotAI/kimi-code --skill review-pr -a claude-code -g -y

安装 repo 全部 skill

npx skills add MoonshotAI/kimi-code --all -g -y

预览 repo 内 skill

npx skills add MoonshotAI/kimi-code --list

SKILL.md

Frontmatter

{
    "name": "review-pr",
    "description": "Use when reviewing a pull request in the kimi-code repository — translate the PR template sections into Chinese and evaluate the change against the template structure.",
    "disable-model-invocation": true
}

Review PR

Review a pull request by evaluating the description against the template and the actual diff, then write a structured review summary in Chinese.

Workflow

Fetch the PR description and metadata:

gh pr view <number> --json title,body,url,files,additions,deletions,baseRefName,headRefName

Read the full diff:
```
gh pr diff <number>
```
Read enough surrounding code to verify the claims in the PR description.
Evaluate each section against the criteria below.
Write the review summary in Chinese.

Section Translation

Use these translated names in the review summary:

English	中文
Requirement or Bug	需求或 Bug
Bug Reproduction Steps	Bug 复现步骤
Root Cause	根本原因
Code Changes	代码变更
Impact Scope	影响范围
Checklist	检查清单

Review Criteria

需求或 Bug

Is the linked issue valid and relevant?
If no issue, is the requirement clearly stated in one or two sentences?

Bug 复现步骤

For bug PRs: are the steps clear and reproducible?
Can you follow the steps to confirm the bug exists on the base branch?

根本原因

For bug PRs: is the root cause convincingly explained?
Does the stated root cause match what you see in the diff?
Is it clear whether this is a fundamental fix or a workaround?

代码变更

Does the description match the actual diff?
Are visual outlines (diff blocks, call trees, file trees) accurate and helpful?
Is the approach sound? Are there simpler alternatives?
Are there edge cases the author missed?

影响范围

Are all affected modules identified? Cross-check with the diff file list.
Does test coverage match the claimed scope?
Are there untested paths that carry risk?

检查清单

Are all applicable items checked?
For items marked as "not needed", do you agree?

Output

Write the review summary in Chinese. For each section:

State whether it is adequately filled in.
Flag anything missing, inaccurate, or inconsistent with the diff.
If the PR is ready, say so. If changes are needed, list them as actionable items.