Reviewing code

Skill bg-szy/TOP-SKILLS/skills/claude-code-skills/reviewing-code

全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard

Install

npx -y skills add bg-szy/TOP-SKILLS --skill reviewing-code

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Get code review from Codex AI for implementation quality, bug detection, and best practices. Use when asked to review code, check for bugs, find security issues, or get feedback on implementation patterns.

SKILL.md

1.6 KB, as published. Nobody here has run it

Code Review with Codex

Use mcp__codex__spawn_agent for code review.

When to Use

Review code quality and patterns
Find potential bugs or edge cases
Validate against best practices
Check for security issues

Usage

{
  "prompt": "Review this code for [quality/bugs/security]: [code or file]"
}

Prompt Examples

"Review for code quality and Go best practices: [code]"
"Analyze for security vulnerabilities: [code]"
"Review for performance issues: [code]"
"Does this follow idiomatic patterns? [code]"

Gotchas

Codex review is non-deterministic — same code with different invocations gets different priority orderings; pin model version when reproducibility matters.
Codex doesn't see staged-but-uncommitted changes by default — pass them explicitly via --include-staged or piped diff.
Diff-only review misses cross-file effects — a renamed function's callsite in another file isn't in the diff, so the rename's blast radius isn't surfaced.
Review output ranks by Codex's internal severity heuristic — not by user-defined priority; re-rank manually for project-specific concerns.
Whitespace-only diffs trigger reviews — pass --ignore-whitespace or you get noise.
Large diffs (>500 LOC) get summarized, not reviewed line-by-line — split into focused reviews per file group.