code-review

星标5

分支0

更新时间2026年6月1日 21:28

Review a change for correctness, edge cases, security, tests, and clarity

安装

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

在 Manus 中运行

来源

New1Direction

New1Direction/korgex

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

下载

在 Manus 中运行

相关职业SOC

基于 SOC 职业分类

软件质量保证分析师与测试员计算机与数学类职业·SOC 15-1253

SKILL.md

readonly

name	code-review
description	Review a change for correctness, edge cases, security, tests, and clarity
version	1
trust	built-in

Review the DIFF, but read enough surrounding code to judge it in context.

Get the diff. git diff (or the relevant range). Read each hunk with its surrounding function and callers — a change is only correct in context.
Check, in priority order:
- Correctness: does it do what it claims? Off-by-one, null/empty, error paths.
- Edge cases: boundaries, concurrency, large/empty inputs, failure modes.
- Security: injection (command/SQL/XSS), path traversal, secrets in code, unvalidated input crossing a trust boundary.
- Tests: is the new behaviour covered? Would a test have caught a regression?
- Clarity: names, dead code, needless complexity, comments that explain WHY.
Verify, don't assume. If unsure a branch is reachable or a value can be null, trace it or write a quick check rather than guessing.
Report findings ranked by severity (blocker → nit), each with file:line and a concrete suggested fix. Call out what's GOOD too. Don't invent issues to seem thorough.

同仓库更多 Skills

同仓库

react-doctor

New1Direction/korgex

Catch bad React in your changes — run react-doctor's deterministic scan and fix what it flags

2026-06-055

security-scan

New1Direction/korgex

Run a verifiable security scan (vulns, secrets, misconfig) over code you wrote or deps you added, before calling the work done

2026-06-035

browser-automation

New1Direction/korgex

Drive a real browser verifiably — navigate, snapshot, act BY INDEX, extract; every step provable

2026-06-025

verifiable-orchestration

New1Direction/korgex

Run multi-agent work as ONE provable causal DAG — parallel subagents, an Orchestrate graph, an immutable spec-seed

2026-06-025

building-an-mcp-server

New1Direction/korgex

Author or connect a Model Context Protocol server so an agent gains new tools

2026-06-015

ci-cd-pipelines

New1Direction/korgex

Build automated pipelines that gate merges and ship reliably

2026-06-015

name	code-review
description	Review a change for correctness, edge cases, security, tests, and clarity
version	1
trust	built-in

Review the DIFF, but read enough surrounding code to judge it in context.

Get the diff. git diff (or the relevant range). Read each hunk with its surrounding function and callers — a change is only correct in context.
Check, in priority order:
- Correctness: does it do what it claims? Off-by-one, null/empty, error paths.
- Edge cases: boundaries, concurrency, large/empty inputs, failure modes.
- Security: injection (command/SQL/XSS), path traversal, secrets in code, unvalidated input crossing a trust boundary.
- Tests: is the new behaviour covered? Would a test have caught a regression?
- Clarity: names, dead code, needless complexity, comments that explain WHY.
Verify, don't assume. If unsure a branch is reachable or a value can be null, trace it or write a quick check rather than guessing.
Report findings ranked by severity (blocker → nit), each with file:line and a concrete suggested fix. Call out what's GOOD too. Don't invent issues to seem thorough.