Run Astro diagnostics on the project. Use when working with .astro files and you need to check for type errors, missing imports, or invalid syntax. Lightweight alternative to the full LSP — runs on demand with zero persistent memory cost.
From astro-checknpx claudepluginhub ricardo-nth/claude-astro-lsp --plugin astro-checkThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Walks every branching path and boundary condition in code, specs, or diffs, reporting only unhandled edge cases.
Run astro check to get diagnostics for all .astro and .ts files in the project.
Detect the package manager by checking for lock files in the project root:
pnpm-lock.yaml → pnpm exec astro checkyarn.lock → yarn astro checkbun.lockb → bun run astro checkpackage-lock.json or fallback → npx astro checkRun the check command from the project root.
If there are errors, analyze the output and fix them. If $ARGUMENTS contains specific file paths, focus on errors in those files.
If there are no errors, confirm the project is clean.
astro check uses the Astro compiler and TypeScript under the hood, catching the same errors the LSP would./plugin enable astro-lsp@claude-astro-lsp (requires session restart).