AGENT SKILL
code-review
Review code changes for bugs, security, and correctness with a high signal-to-noise checklist
- License 许可
- Apache-2.0
- 最近更新
- 2026-07-01
- Stars
- ★ 2
- Forks
- 1
01 前言 Front Matter
- name
- code-review
- description
- Review code changes for bugs, security, and correctness with a high signal-to-noise checklist
03 SKILL.md 正文
Code Review
Use this skill when asked to review a diff, pull request, or a set of changes. The goal is a high signal-to-noise review: surface issues that genuinely matter and stay quiet about trivia.
Process
- Get the changes. Prefer the smallest accurate scope:
git diff(unstaged),git diff --staged, orgit diff <base>...HEADfor a branch.- In an SVN repo use
svn diff.
- Read each changed hunk in the context of the surrounding file, not in isolation.
- For every file, walk the checklist below.
- Report findings grouped by severity. Cite
file:line. Suggest a concrete fix.
What to flag (in priority order)
- Correctness / logic bugs — off-by-one, inverted conditions, wrong operator,
missing
return, unhandlednil/null, incorrect error propagation. - Security — injection (SQL/shell/HTML), unvalidated input, path traversal, secrets committed to source, missing authz checks, unsafe deserialization.
- Resource & concurrency — leaked files/handles/goroutines, missing
defer close, data races, lock ordering, unbounded growth. - Error handling — swallowed errors, errors logged but not handled, panics on recoverable conditions, losing the original error context.
- API & data contracts — breaking changes to public signatures, serialized field renames, ID precision (64-bit IDs must not round-trip through JS numbers).
- Tests — does new behavior have coverage? Do changed paths break existing tests?
What NOT to comment on
- Formatting, import order, or anything a linter/formatter owns.
- Pure style preferences that don't change behavior.
- Speculative "you could also" rewrites unrelated to the change.
Output format
### Blocking
- path/to/file.go:42 — <problem>. <why it matters>. Fix: <concrete suggestion>.
### Non-blocking
- path/to/other.go:13 — <minor concern>.
### Looks good
- <one line on what is solid, if anything notable>
If you found nothing substantive, say so plainly rather than inventing nits.
04 同仓库更多 Skills
parallel-research
Delegate independent research and verification to sub-agents in parallel to cut wall-clock latency
★ 2
git-commit
Write clear Conventional Commits messages and stage changes safely
★ 2
debugging
Systematically find the root cause of a bug instead of guessing at fixes
★ 2
calc
Calculate mathematical expressions
★ 2