Agent skill
codex-codereview
Use for code review and quality feedback from Codex. Triggers on "codex review code", "codex code review", "have codex review this", "get codex feedback on code".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/codex-codereview
SKILL.md
Codex Code Review Skill
Comprehensive code review with Codex (gpt-5.2).
When to Use
- Reviewing code before commit
- Getting feedback on implementation
- Checking for security issues
- Verifying best practices
- Architecture review
Reasoning Level
high (thorough but efficient review)
Execution
- Identify code to review:
- Specific files mentioned by user
- Staged changes (
git diff --staged) - Recent changes (
git diff)
- Gather context about the codebase patterns
- Formulate a review prompt:
Review this code thoroughly. Code: <code to review> Context: <any relevant context about patterns/conventions> Please review for: 1. Bugs and logic errors 2. Security vulnerabilities 3. Performance issues 4. Code quality and readability 5. Best practices adherence 6. Edge cases - Run:
codex exec -c model_reasoning_effort="high" "<prompt>" - Return structured review feedback
Response Format
**Codex Code Review:**
**Summary:**
[Overall assessment]
**Issues Found:**
- 🔴 Critical: [if any]
- 🟡 Warning: [if any]
- 🔵 Suggestion: [if any]
**Detailed Feedback:**
[Line-by-line or section-by-section feedback]
**Recommendations:**
[Specific improvements]
**Session ID:** [id]
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?