Menu
Get an independent review of the current plan
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Add a new language server to loxel with full integration across all layers (build/download, server manager, server routing, client connection, Monaco registration, highlighting/icons, editor URI scheme, packaging). Use when adding support for a new programming language or file type that needs LSP features like completions, hover, diagnostics, or go-to-definition.
Compact the current conversation into a handoff document for another agent to pick up. Use when ending a session, switching contexts, or preparing work for a fresh agent to continue.
Apply Convex implementation rules and review standards for backend work. Use when creating or modifying Convex queries, mutations, actions, HTTP endpoints, schema/indexes, validators, pagination, cron jobs, or TypeScript types in Convex codebases.
Create or improve a Claude Code skill (SKILL.md). Use when building a new skill, reviewing an existing skill for quality, or converting a repeated workflow into a reusable skill.
Generate architecture diagrams as .excalidraw files from codebase analysis. Use when the user asks to create architecture diagrams, system diagrams, visualize codebase structure, generate excalidraw files or describe flows visually.
Explore locally cloned open source package internals in ~/git/open-source/. Use when checking a dependency's internal API, types, behavior, feature availability, or docs — e.g. "how does convex handle pagination", "what args does excalidraw's convertToExcalidrawElements accept", "check if dockview supports custom tab renderers".
| name | review-plan |
| description | Get an independent review of the current plan |
| disable-model-invocation | true |
| context | fork |
| agent | Plan |
You are reviewing a plan. Your job is to find problems — not to validate.
Read the plan file. Then independently explore the codebase and gather your own understanding of the relevant code, constraints, and context. Do not rely on claims in the plan — verify them.
Review for:
Report only substantive issues. Skip stylistic preferences and minor suggestions.
End with a structured summary:
