Reviewing Code
- 89 installs
- 6 repo stars
- Updated July 22, 2026
- julianobarbosa/claude-code-skills
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.
About
Get code review from Codex AI for implementation quality, bug detection, best practices.. Use when reviewing code, checking for bugs, finding security issues, getting feedback.
- beginner skill
- core: code review & quality
Reviewing Code by the numbers
- 89 all-time installs (skills.sh)
- +1 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #470 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/julianobarbosa/claude-code-skills --skill reviewing-codeAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 89 |
|---|---|
| repo stars | ★ 6 |
| Last updated | July 22, 2026 |
| Repository | julianobarbosa/claude-code-skills ↗ |
What it does
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.
Files
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-stagedor 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-whitespaceor you get noise. - Large diffs (>500 LOC) get summarized, not reviewed line-by-line — split into focused reviews per file group.
Related skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264kCode Review & Qualitytesting