원클릭으로 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.