ワンクリックでManusで任意のスキルを実行

始める

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 リポジトリを開く Creator のリポジトリを見る

ダウンロード

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.