Execute comprehensive code reviews using OpenAI Codex CLI. Use when: (1) reviewing git commits by ID or range, (2) reviewing pull requests by number, (3) requesting thorough code quality analysis. Triggers on phrases like "codex review", "review commit", "review PR", "レビュー". Requires codex CLI to be installed and authenticated.
Executes comprehensive code reviews using OpenAI Codex CLI for commits and PRs.
/plugin marketplace add karak/karak-claude-plugin/plugin install karak-karak-claude-plugin@karak/karak-claude-pluginThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/review-perspectives.mdscripts/prepare_review_context.shExecute code reviews via OpenAI Codex CLI with comprehensive analysis.
Before proceeding, verify codex CLI availability:
which codex && codex --version
If codex is not found, inform the user and abort.
Run the context collection script or gather information manually:
# Using script
scripts/prepare_review_context.sh <target>
# Or manually for commits:
git log -1 --format="%H%n%s%n%b" <commit_id>
git diff-tree --no-commit-id --name-status -r <commit_id>
git show <commit_id>
# For PRs:
gh pr view <number> --json title,body,files
gh pr diff <number>
Structure the prompt with these sections:
以下のコードをレビューしてください。
## 1. 対象ファイル
- コミットID/PR: <id>
- 変更ファイル:
- <file1>
- <file2>
## 2. セッションのゴールと受入基準
<what success looks like>
## 3. 解決しようとした課題
<problems being addressed>
## 4. 成果と変更点
<summary of changes>
codex exec --sandbox read-only "<prepared_prompt>"
Critical notes:
exec subcommand (not interactive mode)--sandbox read-only for safetyCodex outputs contain:
thinking - reasoning traces (can be skipped)exec - commands executed by codexcodex or final text - actual review findingsExtract and summarize:
For comprehensive reviews, ensure codex examines these areas. See references/review-perspectives.md for detailed checklist.
| Category | Key Points |
|---|---|
| Correctness | Logic errors, edge cases, null handling |
| Security | Input validation, auth, secrets |
| Performance | N+1 queries, memory leaks, blocking ops |
| Maintainability | Duplication, naming, complexity |
| Testing | Coverage, isolation, assertions |
| Error | Cause | Solution |
|---|---|---|
stdout is not a terminal | Using interactive mode | Use codex exec instead |
command not found | codex not installed | Install via npm/brew |
| Timeout | Large diff or slow network | Increase timeout, split review |
| Auth error | Token expired | Run codex login |
User: codex で最新コミットをレビューして
Claude:
1. Check codex availability: `which codex && codex --version`
2. Collect context:
- git log -1 --format="%H%n%s%n%b" HEAD
- git diff-tree --no-commit-id --name-status -r HEAD
- git show HEAD
3. Prepare prompt with 4 sections
4. Execute: codex exec --sandbox read-only "<prompt>"
5. Summarize findings for user
scripts/prepare_review_context.sh <target> - Collects git context for commit/range/PRThis skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.