reviewing-code · julianobarbosa — Claude Code skill: code review and installation
The reviewing-code skill asks Codex to review code for bugs, security concerns, and implementation practices. Use it when you want a second assessment of a file or change.
MIT 101 installs ★ 17 updated 2026-10-14
npx skills add julianobarbosa/claude-code-skills --skill reviewing-code -a claude-codeWhat reviewing-code does
The skill calls mcp__codex__spawn_agent to send Codex a code-review task. Ask it to assess implementation quality, look for edge cases or security issues, or check a specific snippet for performance concerns and language conventions.
Codex can rank findings differently across runs, so pin the model version when repeatable results matter. Staged changes that have not been committed are outside its default view; large diffs above 500 LOC are summarized rather than checked line by line. Pass staged changes explicitly and split broad reviews into focused file groups.
What it helps with
- spot likely bugs and edge cases
- check code for security flaws
- assess whether an implementation follows language practices
- review code quality and patterns
- identify performance concerns
Example prompts for the agent
- Review
src/auth.tsfor bugs and security risks. - Check this Go snippet against common Go conventions.
- Look over these changes for performance problems and explain the risks you find.
How to install reviewing-code
1Skills CLI (Vercel)
npx skills add julianobarbosa/claude-code-skills --skill reviewing-code -a claude-code2Manually: put the files in place
~/.claude/skills/reviewing-code/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/reviewing-code/
1Skills CLI (Vercel)
npx skills add julianobarbosa/claude-code-skills --skill reviewing-code -a codex2Manually: put the files in place
.agents/skills/reviewing-code/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add julianobarbosa/claude-code-skills --skill reviewing-code -a cursor2Manually: put the files in place
.cursor/skills/reviewing-code/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install julianobarbosa/claude-code-skills skills/reviewing-code2Manually: put the files in place
.github/skills/reviewing-code/SKILL.md1Skills CLI (Vercel)
npx skills add julianobarbosa/claude-code-skills --skill reviewing-code -a gemini-cli2Platform CLI
gemini skills install https://github.com/julianobarbosa/claude-code-skills --path skills/reviewing-codeManually: put the files in place
.devin/skills/reviewing-code/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add julianobarbosa/claude-code-skills --skill reviewing-code -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about reviewing-code
How do I install reviewing-code in Claude Code?
Run npx skills add julianobarbosa/claude-code-skills --skill reviewing-code -a claude-code, then use ~/.claude/skills/reviewing-code/SKILL.md.
What does reviewing-code do?
It sends a review request to Codex, which can examine code quality, potential bugs, security issues, and implementation practices.
Does Codex review staged changes?
Staged changes that have not been committed are not part of Codex's default input. Pass them with --include-staged or provide a diff through a pipe.
Source text
SKILL.md · MIT
---
name: reviewing-code
description: 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.
allowed-tools: Read, Grep, Glob, mcp__codex__spawn_agent
---
# 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
```json
{
"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.
© julianobarbosa · MIT · julianobarbosa/claude-code-skills
Similar skills
All skills for Code review and refactoring →reviewing-code by other authors comes first.