New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Wasp Review

by wasp-lang in wasp-lang/wasp

Review code changes for correctness, clarity, and potential issues.

MITAuto-check passedDevelopment

Install Wasp Review

skills CLI
$ npx skills add wasp-lang/wasp --skill wasp-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install wasp-lang/wasp wasp-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/wasp-lang/wasp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/wasp-review .claude/skills/wasp-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
wasp-review
GitHub stars
19k
Token cost
~834 tokens
SKILL.md length
412 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Review code changes for correctness, clarity, and potential issues.

  • The user asks for a review
  • SKILL.md covers Naming And Vocabulary, Contracts And Interfaces, Readability And Context and Design And Architecture, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Wants feedback on a diff

What it does

Wasp Review is an agent skill from wasp-lang/wasp. Review code changes for correctness, clarity, and potential issues. Use when the user asks for a review, code review, PR review, or wants feedback on a diff or file.

Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Code review and Pull requests. The repository describes itself as: The batteries-included full-stack framework for the AI era. Develop JS/TS web apps (React, Node.js, and Prisma) using declarative code that abstracts away complex full-stack… The licence is MIT.

When your agent uses it

  • The user asks for a review
  • Wants feedback on a diff

Example prompts

  • “/wasp-review”

What it can do on your machine

Read from SKILL.md and the folder at commit 3a90061. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Wasp Review loads about 834 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 412 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~834

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from wasp-lang/wasp at commit 3a90061, republished under its MIT licence (© wasp-lang). 412 words, ~834 tokens.

Download SKILL.mdSave it as .claude/skills/wasp-review/SKILL.md (or your agent's skills folder).
name
wasp-review
description
Review code changes for correctness, clarity, and potential issues. Use when the user asks for a review, code review, PR review, or wants feedback on a diff or file.

Rules

Naming And Vocabulary

  • Demand precise, informative names. Names must not misdirect, omit relevant behavior, or assume unavailable context.
  • Make names accurately reflect what their declarations represent.
  • Context is king: evaluate names within their scope and surrounding vocabulary.
  • Use established codebase terminology consistently.
  • Follow established naming conventions e.g. is... for booleans and ensure... for idempotent setup operations.
  • Treat awkward names as evidence of design problems. If an accurate name becomes excessively long or complicated, inspect whether the declaration has too many responsibilities.
  • Avoid vague names such as data, info, or unexplained single letters.

Contracts And Interfaces

  • Review names before implementation details. Poor names often expose deeper problems in decomposition and architecture.
  • Declaration should be enough to understand, without the implementation. A function’s name, arguments, types, and contract should explain its behavior.

Readability And Context

  • Demand code to be easy to read. Understanding one section should not require reading the entire file.
  • Review from the perspective of a developer with minimal reasonable context.

Design And Architecture

  • Treat and or then in a function name as a possible responsibility smell.
  • Treat groups of similarly prefixed parameters as possible missing abstractions.
  • Make sure the code is DRY. Introduce helpers for commonly repeated concepts.
  • Identify hidden assumptions. Require assumptions to be enforced through types, runtime checks, or comments, in that order.
  • Check for Effective TypeScript defined problems.
  • Avoid NIH: check existing code and dependencies before introducing abstractions or helpers, share code once it has multiple consumers.
Show full SKILL.md (170 more words)Show less

Comments And Writing

  • Prefer improving design or naming; use comments only when code cannot communicate enough.
  • Remove comments that preserve session-specific context unnecessary to a fresh reader.
  • Use comments only for information that names, arguments, and types cannot express.
  • Remove comments that merely narrate obvious code or exhibit generated filler.
  • Suggest pruning fluff and no-op sentences from prose.

Code Smells

  • Primitive Obsession: identify strings and primitives representing domain concepts that need dedicated types.
  • Shotgun Surgery: flag one logical change scattered across unrelated files.
  • Divergent Change: flag modules carrying several unrelated responsibilities.
  • Repeated Switches: flag code that repeatedly handles the same cases in different places.
  • Speculative Generality: reject abstractions and configuration without a current requirement.
  • Middle Man: flag layers that only forward calls without enforcing a boundary or adding meaning.

Other

  • Check whether requested improvements justify their implementation cost.

Findings And Reporting

  • Make every finding actionable. Include the file and line, explain the problem, and suggest a concrete fix.
  • Use code snippets when they make the problem or proposed fix clearer.

© wasp-lang, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/wasp-review of wasp-lang/wasp.

Open the folder on GitHubat commit 3a90061

Compare with similar skills

Wasp Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Wasp Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Wasp Review this skillwasp-lang/wasp19k—~834Automated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence
Open Code Review CLIalibaba/open-code-review46k—~3.1kAutomated safety check: PassApache-2.0
GitHub Review Iterationprisma/orm48k—~2.2kAutomated safety check: PassApache-2.0
Understand Diff AnalysisEgonex-AI/Understand-Anything86k—~1.4kAutomated safety check: PassMIT

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Open Code Review CLI

    alibaba/open-code-review

    Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.

    46k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Code Review

    flutter/flutter

    Performs a comprehensive, multi-step code review of pull requests or local code changes, using iterative refinement (generation, critique, synthesis) to ensure high-quality, actionable feedback.

    180k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed

More from wasp-lang/wasp

  • Geo Fundamentals

    wasp-lang/wasp

    Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).

    19k GitHub starsUsed in 9 repos~861 tokens
    Auto-check passed

  • Crossposting

    wasp-lang/wasp

    Crosspost Wasp blog articles (MDX) to DEV.to and Medium. An agent skill from wasp-lang/wasp.

    19k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Notion To Blog

    wasp-lang/wasp

    Transfer a blog post from Notion to the Wasp blog. An agent skill from wasp-lang/wasp.

    19k GitHub stars~922 tokensUpdated today
    Auto-check passed

Categories

Questions about Wasp Review

What does Wasp Review do?

Review code changes for correctness, clarity, and potential issues. Wasp Review is an agent skill from wasp-lang/wasp. Review code changes for correctness, clarity, and potential issues.

When should I use Wasp Review?

Wasp Review fits situations like: the user asks for a review; wants feedback on a diff.

How do I install Wasp Review in Claude Code?

Run `npx skills add wasp-lang/wasp --skill wasp-review -a claude-code`. Or copy the skill folder (.agents/skills/wasp-review in wasp-lang/wasp) into .claude/skills/wasp-review in your project. Claude Code loads it when a task matches its description.

How do I install Wasp Review in Codex?

Run `npx skills add wasp-lang/wasp --skill wasp-review -a codex`. Or copy the skill folder (.agents/skills/wasp-review in wasp-lang/wasp) into .agents/skills/wasp-review in your project. Codex loads it when a task matches its description.

Can I use Wasp Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wasp-lang/wasp --skill wasp-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wasp-review, .gemini/skills/wasp-review, .github/skills/wasp-review and .opencode/skills/wasp-review in your project.

What does Wasp Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Wasp Review is instructions for the agent only.

Does Wasp Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Wasp Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Wasp Review use?

Wasp Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Wasp Review use?

About 834 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Wasp Review?

Skills that share tags, products or a category with Wasp Review: PR Babysitter (openinterpreter/openinterpreter, 69k stars), WooCommerce Code Review (woocommerce/woocommerce, 11k stars), Open Code Review CLI (alibaba/open-code-review, 46k stars) and GitHub Review Iteration (prisma/orm, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Wasp Review?

wasp-lang (a GitHub organization) maintains it in wasp-lang/wasp, which has 18,762 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 10, 2026.

Source: wasp-lang/wasp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.