Skill

check

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-check

Install

Run in your terminal

npx claudepluginhub ricardo-nth/claude-astro-lsp --plugin astro-check

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.7k

claude-opus-4-5-migration

2 files

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.

claude-opus-4-5-migration

83.2k

bmad-review-edge-case-hunter

Walks every branching path and boundary condition in code, specs, or diffs, reporting only unhandled edge cases.

bmad-pro-skills

43.8k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitFeb 28, 2026

Actions

View Source View Plugin View on GitHub View README

Instructions

Detect the package manager by checking for lock files in the project root:

pnpm-lock.yaml → pnpm exec astro check
yarn.lock → yarn astro check
bun.lockb → bun run astro check
package-lock.json or fallback → npx astro check

Run 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.

Notes

This is a zero-cost alternative to the full Astro LSP plugin. No persistent language server process — just runs the check and exits.

astro check uses the Astro compiler and TypeScript under the hood, catching the same errors the LSP would.

For heavy editing sessions where you want persistent real-time diagnostics instead, enable the full LSP: /plugin enable astro-lsp@claude-astro-lsp (requires session restart).

Astro Check

Run astro check to get diagnostics for all .astro and .ts files in the project.

Instructions

Detect the package manager by checking for lock files in the project root:
- pnpm-lock.yaml → pnpm exec astro check
- yarn.lock → yarn astro check
- bun.lockb → bun run astro check
- package-lock.json or fallback → npx astro check
Run 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.

Notes

This is a zero-cost alternative to the full Astro LSP plugin. No persistent language server process — just runs the check and exits.
astro check uses the Astro compiler and TypeScript under the hood, catching the same errors the LSP would.
For heavy editing sessions where you want persistent real-time diagnostics instead, enable the full LSP: /plugin enable astro-lsp@claude-astro-lsp (requires session restart).