jezweb/claude-skills / plugins/dev-tools/skills/codex-review
codex-review
VerifiedRun an independent code review using the OpenAI Codex CLI in headless mode. Gets a second opinion from a different model family (the current Codex models) on recent changes, a PR, a commit, or the whole app — covering bugs, regressions, security, data consistency, UX/state bugs, performance risks, and testing gaps. Saves a severity-prioritised report to .jez/reviews/. Triggers: 'codex review', 'review with codex', 'independent code review', 'what does codex think', 'get codex to review'.
prompt.md
View on GitHubReview the entire app for bugs, regressions, edge cases, security issues, data consistency problems, UX/state bugs, performance risks, and testing gaps. Treat this as a code review.
Prioritize findings by severity (critical / high / medium / low / nit), include file/line references for every finding, list open questions and assumptions you had to make, and mention what you verified with typecheck, lint, and tests (and what you couldn't verify).
Be concrete. Prefer "auth.ts:42 — SQL query concatenates user input, vulnerable to injection" over "watch out for SQL injection". If something looks wrong but you're not sure, say so and explain what you'd need to confirm it.
Structure the output as:
## Summary
One-paragraph overview: overall health, biggest concerns, what's solid.
## Critical
Issues that break things, lose data, or expose security holes. Each: file:line, what's wrong, why it matters, suggested fix.
## High
Bugs, regressions, meaningful edge cases.
## Medium
Code quality issues that will bite later — error handling gaps, fragile patterns, missing validation.
## Low / Nits
Style, naming, minor improvements.
## Testing gaps
What should be tested but isn't. What existing tests might miss.
## Open questions & assumptions
What you weren't sure about. What you assumed. What the author should confirm.
## Verification performed
What you ran (typecheck, lint, tests) and the results. What you couldn't run and why.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |