Wasp Code Review FAQs

Question 1

What specific Wasp features does it audit?

Accepted Answer

It audits main.wasp entity listings, server-side operation type annotations, ShadCN library version locking, Prisma enum import paths, and client-side action usage patterns (direct calls vs. useAction hook) to ensure the framework's features are used as intended.

Question 2

When should I use this skill?

Accepted Answer

You should trigger this skill whenever you are reviewing pull requests, checking code before a commit, or performing architectural reviews of new features. It is particularly useful for identifying Wasp-specific nuances that generic linting tools or standard AI models might overlook.

Question 3

How does this skill improve my development workflow?

Accepted Answer

It reduces manual review time by automatically catching common Wasp mistakes, such as incorrect @src vs wasp/ imports, missing type annotations on operations, and improper HTTP error sequencing. This leads to higher code quality, fewer production bugs, and stricter adherence to TDD standards.

Question 4

Does it handle Wasp-specific security requirements?

Accepted Answer

Yes. The skill is hard-coded to enforce security-first patterns, ensuring that authentication checks are the first line of every operation and that multi-tenant isolation is strictly maintained to prevent data leaks between users.

Question 5

What does the Wasp Code Review skill do?

Accepted Answer

This skill provides a specialized auditing layer for Claude Code, specifically designed for the Wasp framework. It scans your code for architectural compliance, enforces mandatory security patterns like server-side auth checks, validates Wasp-specific import rules, and ensures entity listings are configured for optimal performance and auto-invalidation.

Wasp Code Review

Wasp Code Review

Key Features

Use Cases

Key Features

Use Cases