review-criteria
Criteria for reviewing Codex worker outputs across 5 dimensions. Use when reviewing code submitted by workers before approval.
What this skill does
# Review Criteria Skill
This skill defines how the CEO (Claude) reviews outputs from Codex workers.
## Review Framework
Every Codex output must be reviewed across 5 dimensions:
### 1. Completeness (Required)
**Question**: Did the worker do what was asked?
**Checklist**:
- [ ] All files in task specification were created/modified
- [ ] The "Do" instruction was followed
- [ ] Output contains completion signal (TASK_COMPLETE)
**Fail Conditions**:
- Missing files that were specified
- Partial implementation with TODO comments
- No completion signal
### 2. Acceptance Criteria (Required)
**Question**: Does the output meet all acceptance criteria?
**Process**:
```markdown
For each acceptance criterion in the task:
- [ ] AC-1: {criterion} → PASS/FAIL: {reason}
- [ ] AC-2: {criterion} → PASS/FAIL: {reason}
- [ ] AC-3: {criterion} → PASS/FAIL: {reason}
Criteria Met: {passed}/{total}
```
**Fail Conditions**:
- Any P0/P1 criterion fails
- More than 50% of criteria fail
### 3. Code Quality (Required)
**Question**: Is the code well-written?
| Aspect | Weight | Check |
|--------|--------|-------|
| Patterns | High | Follows existing codebase patterns |
| Bugs | High | No obvious logical errors |
| Error Handling | Medium | Proper try/catch, null checks |
| Readability | Medium | Clear naming, reasonable complexity |
| Security | High | No obvious vulnerabilities |
**Fail Conditions**:
- Doesn't follow existing patterns
- Contains obvious bugs
- Missing critical error handling
- Security vulnerability present
### 4. Integration (Required)
**Question**: Will this work with existing code?
**Checklist**:
- [ ] Imports are correct and exist
- [ ] Exports match expected interface
- [ ] No circular dependencies
- [ ] Types are compatible (if TypeScript)
**Fail Conditions**:
- Broken imports
- Type mismatches
- Circular dependency introduced
### 5. Completeness of Output (Optional)
**Question**: Is the output complete and usable?
**Checklist**:
- [ ] No placeholder comments (`// TODO`, `// FIXME`)
- [ ] No incomplete implementations
- [ ] No `...` or ellipsis in code
- [ ] File contents are complete
**Fail Conditions**:
- Contains placeholder code
- Implementation is skeletal
## Review Decision Matrix
| Completeness | Criteria | Quality | Integration | Decision |
|--------------|----------|---------|-------------|----------|
| ✓ | ✓ | ✓ | ✓ | APPROVED |
| ✓ | ✓ | ✗ | ✓ | NEEDS_REVISION |
| ✓ | ✗ | ✓ | ✓ | NEEDS_REVISION |
| ✓ | ✓ | ✓ | ✗ | NEEDS_REVISION |
| ✗ | - | - | - | NEEDS_REVISION |
| - | ✗✗ | - | - | ESCALATE (if max retries) |
## Writing Review Feedback
### For APPROVED
```markdown
## Review: Task {id} - APPROVED ✓
All criteria met. Output is ready for verification.
**Summary**:
- Completeness: PASS
- Acceptance: {n}/{n} criteria met
- Quality: Good
- Integration: Compatible
```
### For NEEDS_REVISION
```markdown
## Review: Task {id} - NEEDS_REVISION ↻
Attempt {n} of {max}. Issues found:
**Issue 1**: {Specific issue}
- File: {path}
- Line: {number} (if applicable)
- Current: {what's wrong}
- Expected: {what's needed}
- Fix: {specific instruction}
**Issue 2**: {Specific issue}
- Fix: {specific instruction}
**Focus Areas for Retry**:
1. {Priority 1}
2. {Priority 2}
```
### For ESCALATE
```markdown
## Review: Task {id} - ESCALATE ⚠️
Max retries ({max}) reached or blocking issue found.
**Reason for Escalation**: {why}
**Attempts Summary**:
| Attempt | Issue | Feedback Given |
|---------|-------|----------------|
| 1 | {issue} | {feedback} |
| 2 | {issue} | {feedback} |
| 3 | {issue} | {feedback} |
**Options for User**:
1. Provide additional guidance and retry
2. Manually implement this task
3. Skip this task (if [OPTIONAL])
4. Modify requirements
```
## Quality Standards
### Code Pattern Matching
When reviewing, compare against:
1. Files in the same directory
2. Similar components/functions in codebase
3. Patterns specified in design.md
4. Project style guide (if exists)
### Common Issues to Watch For
**JavaScript/TypeScript**:
- Missing async/await
- Unhandled promise rejections
- Incorrect this binding
- Missing type annotations
**React**:
- Missing key props in lists
- Direct state mutation
- Missing dependency arrays in hooks
- Memory leaks (missing cleanup)
**API/Backend**:
- Missing input validation
- SQL injection risks
- Missing authentication checks
- Improper error responses
## Iteration Limits
| Task Type | Max Iterations | Escalate After |
|-----------|----------------|----------------|
| Standard | 3 | 3 failures |
| [CRITICAL] | 5 | 5 failures |
| [OPTIONAL] | 2 | Skip after 2 |
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.