antoniocascais/codex
skills/codex/SKILL.md
AI peer review via OpenAI Codex CLI. Use when reviewing code changes, validating technical decisions, comparing implementation approaches, or getting a second opinion on architecture choices. Triggers on /codex, /codex-review, or auto-triggers when presenting significant alternatives to user.
$ install --global
skillsauthnpx skillsauth add antoniocascais/claude-code-toolkit codexInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 9:42 PM1.9s1 file scanned
SKILL.md
- name:
- codex
- description:
- AI peer review via OpenAI Codex CLI. Use when reviewing code changes, validating technical decisions, comparing implementation approaches, or getting a second opinion on architecture choices. Triggers on /codex, /codex-review, or auto-triggers when presenting significant alternatives to user.
- - Bash(codex exec:
- *)
- - Bash(git status:
- *)
- - Bash(git diff:
- *)
- - Bash(git log:
- *)
- user-invocable:
- true
Codex Peer Review
Consult OpenAI's Codex CLI for peer review before presenting significant decisions or completed work to user.
When to Auto-Trigger (Without Explicit /codex)
Auto-consult Codex when about to:
- Present 2+ alternative approaches to solve a problem
- Complete a significant feature implementation
- Propose architectural decisions
- Suggest refactoring strategies
- Present trade-off analysis
Skip auto-consultation for:
- Trivial fixes (typos, formatting, simple one-liners)
- Direct user instructions with no ambiguity
- Information lookups / explanations
- When user explicitly said "just do X"
Codex CLI Reference
Code Review (Scoped)
# Review uncommitted changes (staged + unstaged + untracked)
codex exec review --uncommitted "Focus on: <specific concerns>"
# Review against base branch
codex exec review --base main "Focus on: <specific concerns>"
# Review specific commit
codex exec review --commit <SHA> "Focus on: <specific concerns>"
Freeform Consultation
# Tech decisions, architecture questions, approach validation
codex exec "Given context X, should we use approach A or B? Consider: <factors>"
Prompt Crafting
Claude decides how to prompt Codex. Guidelines:
- Be specific about what feedback you want
- Provide relevant context (file names, constraints, goals)
- For code review: mention what changed and why
- For decisions: frame the trade-offs clearly
Review Loop Protocol
Max Iterations: 3
Execute up to 3 rounds of Claude ↔ Codex exchange:
-
Round 1: Initial consultation
- Send context + question/code to Codex
- Receive Codex's feedback
-
Round 2 (if disagreement): Counter-argument
- If Claude disagrees with Codex's assessment, argue back
- Provide reasoning for disagreement
- Ask Codex to reconsider or clarify
-
Round 3 (if still unresolved): Final exchange
- Last attempt at consensus
- If still disagreeing, note the impasse
Disagreement Handling
Do NOT blindly accept Codex feedback. Evaluate critically:
- Does the suggestion align with project conventions?
- Is the concern valid given the specific context?
- Would the change actually improve the code/decision?
If Claude disagrees:
codex exec "You suggested X, but I disagree because Y. The context you may have missed: Z. Please reconsider or explain why X is still better."
Iteration Limit Reached
If 3 rounds pass without consensus, notify user:
⚠️ Codex review: Reached iteration limit without consensus
**Point of contention**: [what we disagreed on]
**Claude's position**: [your stance + reasoning]
**Codex's position**: [their stance + reasoning]
Proceeding with: [which approach and why]
Output Format
After consultation completes, summarize for user:
## Codex Review Summary
**Consulted on**: [code changes | tech decision | architecture]
**Consensus reached**: Yes/No (N rounds)
### Key Points
- [Agreement 1]
- [Agreement 2]
### Disagreements (if any)
| Topic | Claude | Codex | Resolution |
|-------|--------|-------|------------|
| ... | ... | ... | ... |
### Final Decision
[What was decided and brief rationale]
Invocation Modes
Explicit: /codex or /codex-review
User explicitly requests peer review. Always execute full loop.
Auto-trigger
When about to present alternatives or complete significant work:
- Pause before responding to user
- Run Codex consultation
- Incorporate feedback (or note disagreement)
- Then present to user with review summary
Examples
Code Review (Uncommitted Changes)
codex exec review --uncommitted "Review this authentication refactor. Key changes: moved from session-based to JWT. Check for security issues and edge cases."
Architecture Decision
codex exec "Building a real-time notification system. Options: A) WebSockets with Redis pub/sub, B) Server-Sent Events with PostgreSQL NOTIFY, C) Polling with caching. Constraints: <1000 concurrent users, existing PostgreSQL infra, team familiar with Redis. Which approach and why?"
Validating Trade-offs
codex exec "User asked for feature X. I'm proposing to implement it via Y because of Z. Are there approaches I'm missing? Any concerns with Y?"
Related Skills
antoniocascais/workflow-review
tools
VerifiedTrustedCommunity
Reviews Claude Code sessions and proposes workflow improvements. Use when: (1) /workflow-review command, (2) "review my workflow", "how can I improve", (3) after long sessions when nudged, (4) start of session with pending review. Analyzes tool usage patterns, CLAUDE.md configuration, and compares against CC best practices. Proposes: CLAUDE.md updates, new skills, underused CC features. Saves session summaries to .claude/workflow-reviews/ for cross-session continuity.
5SKILL.mdUpdated Apr 4, 2026
antoniocascais/voice-mode
devops
VerifiedTrustedCommunity
Activates voice conversation mode using Pocket TTS Docker container. Use when user says "voice mode", "let's talk", "talk to me", "speak your responses", or wants Claude to respond with spoken audio. Speaks all responses through TTS and plays via speakers.
5SKILL.mdUpdated Apr 4, 2026
antoniocascais/test-quality
testing
VerifiedTrustedCommunity
Guides strong, effective unit test generation using proven testing techniques. Use when writing unit tests, reviewing test quality, improving existing tests, generating test cases, checking test coverage strength, or when tests exist but may be weak. Triggers on: unit test, test quality, test coverage, write tests, improve tests, review tests, test strength, mutation testing, boundary testing.
5SKILL.mdUpdated Apr 4, 2026
antoniocascais/skill-forge
development
VerifiedTrustedCommunity
Creates new Claude Code skills with proper structure and best practices. Use when user wants to create a skill, update an existing skill, add a new command, scaffold a workflow, define skill hooks, or asks "how do I make a skill".
5SKILL.mdUpdated Apr 4, 2026