一键在 Manus 中运行任何 Skill

开始使用

code-review

星标2

分支0

更新时间2026年5月16日 00:07

Review code for correctness, maintainability, security, and project fit.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

kodi

kodi/topchester-agent

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Code Review

When to Use

Use when reviewing code before merge, after a risky change, or when the user asks for a review.

Procedure

Inspect the diff and the surrounding code that gives it meaning.
Look first for bugs, regressions, missing tests, security issues, and broken contracts.
Check whether the change follows local style, naming, error handling, and dependency patterns.
Keep findings concrete with file and line references when possible.
Put findings before summaries. If there are no findings, say that clearly and mention remaining test gaps.

Verification

Confirm the relevant tests, type checks, lint checks, or manual checks for the changed behavior.

同仓库更多 Skills

同仓库

topchester

kodi/topchester-agent

Explain Topchester commands, configuration, knowledge-base behavior, skills, hooks, sessions, and troubleshooting using packaged product guidance and current workspace facts.

2026-07-172

topchester-config

kodi/topchester-agent

Configure Topchester project and user settings. Use when editing or explaining `topchester.jsonc`, `~/.config/topchester/config.jsonc`, model providers, command policy, ignore paths, hooks, project instruction files, or repo-scoped command approvals.

2026-07-152

plan

kodi/topchester-agent

Split larger work into ordered, verifiable implementation slices.

2026-05-162

repo-orientation

kodi/topchester-agent

Quickly map an unfamiliar repository before changing it.

2026-05-162

systematic-debugging

kodi/topchester-agent

Debug failures by finding evidence and root cause before changing code.

2026-05-162

test-driven-development

kodi/topchester-agent

Add or tighten tests before implementing a behavior change.

2026-05-162

name	code-review
description	Review code for correctness, maintainability, security, and project fit.

Code Review

When to Use

Use when reviewing code before merge, after a risky change, or when the user asks for a review.

Procedure

Inspect the diff and the surrounding code that gives it meaning.
Look first for bugs, regressions, missing tests, security issues, and broken contracts.
Check whether the change follows local style, naming, error handling, and dependency patterns.
Keep findings concrete with file and line references when possible.
Put findings before summaries. If there are no findings, say that clearly and mention remaining test gaps.

Verification

Confirm the relevant tests, type checks, lint checks, or manual checks for the changed behavior.