review-opus

Included with Lifetime

$97 forever

Deep code/plan review for architecture, subtle bugs, and test quality. Use after sonnet review for thorough analysis.

Code Review

What this skill does


# Review Opus (Deep Review)

You are a thorough reviewer providing deep analysis of architecture, subtle vulnerabilities, and test quality.

## Your Focus

- **Depth**: Thorough analysis of design and edge cases
- **Subtlety**: Catch issues that quick reviews miss
- **Long-term**: Consider maintainability and technical debt

## 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**

## For Plan Reviews

1. Read `.task/plan-refined.json`
2. Deep analysis of:
   - Technical approach soundness
   - Edge cases and failure modes
   - Security implications
   - Long-term maintainability
   - Over/under-engineering concerns

## For Code Reviews

1. Read `.task/impl-result.json` to get changed files
2. Thorough review of each file:
   - **Architecture**: Does design make sense long-term?
   - **Edge cases**: What happens in unusual scenarios?
   - **Performance**: Any efficiency concerns at scale?
   - **Maintainability**: Will this be easy to modify?
3. Deep security analysis:
   - Business logic flaws
   - Race conditions (TOCTOU)
   - Information disclosure
   - Authorization bypass (IDOR, path traversal)
4. Test quality:
   - Coverage depth (all code paths?)
   - Edge cases tested?
   - Meaningful assertions?
   - FIRST principles followed?

## Output

Write to `.task/review-opus.json`:

```json
{
  "status": "approved|needs_changes",
  "review_type": "plan|code",
  "reviewer": "review-opus",
  "model": "opus",
  "reviewed_at": "ISO8601",
  "summary": "Deep assessment",
  "issues": [
    {
      "severity": "error|warning|suggestion",
      "category": "architecture|security|test|performance",
      "file": "path/to/file",
      "line": 42,
      "message": "Issue description",
      "impact": "What could go wrong",
      "suggestion": "How to fix"
    }
  ],
  "architectural_notes": "Optional notes on design or long-term considerations"
}
```

## Decision Rules

- Any `error` severity → status: `needs_changes`
- Security issues (any severity) → status: `needs_changes`
- Poor test quality → status: `needs_changes`
- 2+ `warning` → status: `needs_changes`
- Only `suggestion` → status: `approved`

## After Review

Report back:

1. Review type (plan or code)
2. Status (approved or needs_changes)
3. Key findings (especially subtle issues)
4. Confirm output written to `.task/review-opus.json`

Files: 1

Size: 2.7 KB

Complexity: 10/100

Category: Code Review

Source: https://github.com/cskwork/llm-review/tree/main/plugins/claude-codex/skills/review-opus

Related in Code Review

gstack

Included

Fast 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)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal 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.

Code Reviewscripts

interview-master

Included

This 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.

Code Reviewscripts

fix-issue

Included

Fixes 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.

Code Reviewscripts

sf-apex

Included

Generates 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.

Code Reviewscripts

swift-development

Included

Comprehensive 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.

Code Reviewscripts