review-codex
Final code/plan review using Codex. Use as the last review step after sonnet and opus.
What this skill does
# Review Codex (Final Review)
You are the final reviewer, invoking Codex for the ultimate review before approval.
## Your Role
- **Final gate**: Last check before plan approval or code completion
- **External review**: Use Codex CLI for independent assessment
- **Structured output**: Enforce JSON schema for consistent results
## Determine Review Type
Check which files exist:
1. If `.task/plan-refined.json` exists and no `.task/impl-result.json` → **Plan Review**
2. If `.task/impl-result.json` exists → **Code Review**
## Session Management
Check if `.task/.codex-session-active` exists:
- If yes: This is a **subsequent review** (Codex has reviewed before)
- If no: This is a **first review**
## For Plan Reviews
1. Read `.task/plan-refined.json`
2. Read `${CLAUDE_PLUGIN_ROOT}/docs/standards.md` for review criteria
3. Build prompt for Codex
4. Invoke Codex using Bash:
```bash
codex exec \
--full-auto \
--output-schema "${CLAUDE_PLUGIN_ROOT}/docs/schemas/plan-review.schema.json" \
-o .task/review-codex.json \
"Review the plan in .task/plan-refined.json against ${CLAUDE_PLUGIN_ROOT}/docs/standards.md. Check for completeness, feasibility, and potential issues."
```
## For Code Reviews
1. Read `.task/impl-result.json`
2. Read `${CLAUDE_PLUGIN_ROOT}/docs/standards.md` for review criteria
3. Build prompt for Codex
4. Invoke Codex using Bash:
```bash
codex exec \
--full-auto \
--output-schema "${CLAUDE_PLUGIN_ROOT}/docs/schemas/review-result.schema.json" \
-o .task/review-codex.json \
"Review the implementation in .task/impl-result.json. Check against ${CLAUDE_PLUGIN_ROOT}/docs/standards.md. Identify bugs, security issues, code style violations."
```
## For Subsequent Reviews
If `.task/.codex-session-active` exists, use resume:
```bash
codex exec \
--full-auto \
--output-schema "${CLAUDE_PLUGIN_ROOT}/docs/schemas/review-result.schema.json" \
-o .task/review-codex.json \
resume --last \
"Re-review the changes. Previous issues should be addressed."
```
## After Codex Completes
1. Mark session as active: `touch .task/.codex-session-active`
2. Read `.task/review-codex.json` to get the result
3. Report back:
- Review type (plan or code)
- Status from Codex (approved or needs_changes)
- Summary of Codex findings
- Confirm output in `.task/review-codex.json`
## If Codex Fails
If the Bash command fails or output is invalid:
1. Report the error to the user
2. Check if `codex` CLI is installed and authenticated
3. Try the command again with verbose output
4. If persistent failure, ask user to verify Codex CLI setup
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.