reviewing-code
Code review checkpoint using codex review CLI. Returns structured result with pass/fail status and issues. Use when: 'code review', 'review changes', 'codex review', 'check my code'.
What this skill does
# Codex Review Checkpoint
Code review checkpoint that runs `codex review` on the current worktree.
**Note:** The gate-runner script runs this automatically for issues with `gate:codex-review` label. This skill documents the process for manual use.
## Quick Start
```bash
# Review uncommitted changes
codex review --uncommitted --title "My Review"
# Review branch changes against main
codex review --base main --title "Feature Review"
# Review a specific commit
codex review --commit abc123
```
## What This Skill Does
1. Determines what to review (uncommitted changes vs branch diff)
2. Runs `codex review` (non-interactive, exits on completion)
3. Parses results into structured format
4. Writes result to checkpoint file
## Workflow
### Step 1: Determine Review Scope
```bash
# Check for uncommitted changes
git status --porcelain
# Check for branch diff
git diff --quiet main...HEAD && echo "No branch changes" || echo "Has branch changes"
```
### Step 2: Run Codex Review
```bash
# For uncommitted changes
codex review --uncommitted --title "Checkpoint Review"
# For branch diff against main
codex review --base main --title "Checkpoint Review"
```
Codex review:
- Runs non-interactively (no terminal interaction needed)
- Outputs structured findings with severity levels (P1, P2, P3)
- Exits with appropriate status
### Step 3: Parse and Write Result
After reviewing, create a structured result:
```json
{
"checkpoint": "codex-review",
"timestamp": "2026-01-19T12:00:00Z",
"passed": true,
"issues": [],
"summary": "No critical issues found"
}
```
**Result Fields:**
- `passed`: true if no P1/P2 issues found
- `issues`: array of `{severity, message, file?, line?}`
- `summary`: brief human-readable summary
### Step 4: Write Checkpoint File
```bash
mkdir -p .checkpoints
cat > .checkpoints/codex-review.json << 'EOF'
{
"checkpoint": "codex-review",
"timestamp": "...",
"passed": true,
"issues": [],
"summary": "..."
}
EOF
```
## Decision Criteria
**Pass if:**
- No P1 or P2 issues found
- No security vulnerabilities detected
- No obvious bugs or logic errors
**Fail if:**
- P1/P2 issues found
- Security issues found
- Critical bugs detected
## Example Output
```
$ codex review --uncommitted --title "Feature Review"
OpenAI Codex v0.87.0 (research preview)
--------
workdir: /home/user/project
model: gpt-5.2
...
[P2] Guard against missing script before execution — path/to/file.sh:45
Description of the issue...
[P3] Consider adding error handling — path/to/other.ts:120
Suggestion details...
```
## Automated Usage
The `gate-runner.sh` script runs codex review automatically:
```bash
./plugins/conductor/scripts/gate-runner.sh --issue ISSUE-ID --worktree /path/to/worktree
```
This:
1. Checks issue labels for `gate:codex-review`
2. Runs `codex review` directly (no terminal spawn needed)
3. Writes checkpoint to `.checkpoints/codex-review.json`
4. Returns pass/fail status
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.