review

Included with Lifetime

$97 forever

Review a plan with Momus

Code Review

What this skill does


[DELEGATION REQUIRED]

You must delegate this review to the Momus agent with criteria tailored to the artifact type.

## Artifact Type Detection

Determine the artifact type from the file path provided in `$ARGUMENTS`:

| Path Pattern | Artifact Type |
|-------------|--------------|
| `.olympus/plans/*` | Plan |
| `*/inception/intent.md` | Intent |
| `*/inception/user-stories/*` | User Stories |
| `*/inception/units/unit-of-work*.md` | Unit Decomposition |
| `*/construction/*-code-generation-plan.md` | Code-Generation Plan |
| `*/inception/application-design/components.md` or `*/inception/application-design/services.md` | Design Docs |
| `*/audit.md` | Audit Trail |
| No path provided | Plan (default — review latest plan in `.olympus/plans/`) |
| Unknown path | Generic |

## Per-Artifact Evaluation Criteria

Based on the detected artifact type, use these criteria:

**Plan**: Clarity (80%+ claims cite file/line refs), Testability (90%+ criteria testable), Verification (file refs exist), Specificity (no vague terms without metrics)

**Intent**: Problem clarity, Scope boundaries defined, Measurable success criteria, Constraint completeness, Exclusions defined, Persona coverage

**User Stories**: INVEST compliance, Acceptance criteria testability, Persona coverage, No orphaned stories

**Unit Decomposition**: Unit independence, Story coverage completeness, Dependency validity, No circular deps

**Code-Generation Plan**: Scope fits single unit, Feasibility, Test plan present, Risk identification, Consistency with unit spec

**Design Docs**: Consistency with intent, Component completeness, Interface definitions, Dependency accuracy

**Audit Trail**: Completeness (all decisions recorded), Traceability to requirements, Gate decisions documented

**Generic**: Structure, Completeness, Internal consistency, Actionability

## Dispatch to Momus

**IMMEDIATELY** use the Task tool:

```
Task(
  subagent_type="momus",
  description="Artifact review",
  prompt="""
$ARGUMENTS

Detect the artifact type from the file path and apply the appropriate evaluation criteria listed above.
If no path is provided, review the most recent plan in `.olympus/plans/`.

Provide one of these verdicts:
- **APPROVED** - Artifact meets all criteria
- **REVISE** - Issues found (provide specific feedback)
- **REJECT** - Fundamental problems

After your review, save the review output as a sibling file:
- Name it `{artifact-name}-review.md` in the same directory as the reviewed file
- Include metadata at the top: reviewer (momus), trigger (manual), trust level (from .olympus/trust-state.json), verdict
- Example: reviewing `intent.md` → save review to `intent-review.md`
  """
)
```

**DO NOT** attempt to review the artifact yourself - you must spawn the Momus agent.

Files: 1

Size: 2.8 KB

Complexity: 4/100

Category: Code Review

Source: https://github.com/mikev10/olympus/tree/main/resources/skills/review

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