reviewing-code

Q: How do I install reviewing-code?

Run npx skills add https://github.com/julianobarbosa/claude-code-skills --skill reviewing-code in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/reviewing-code/ (personal) or .claude/skills/reviewing-code/ (project).

by julianobarbosaCode Quality & Workflow

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.

Installs: 100
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/julianobarbosa/claude-code-skills --skill reviewing-code

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads reviewing-code automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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.

FAQ

What does the reviewing-code skill do?

How do I install reviewing-code?

Run npx skills add https://github.com/julianobarbosa/claude-code-skills --skill reviewing-code in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/reviewing-code/ (personal) or .claude/skills/reviewing-code/ (project).

Which AI agents can use reviewing-code?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is reviewing-code safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains reviewing-code?

It is published by julianobarbosa in julianobarbosa/claude-code-skills. It has 100 recorded installs.