Stats
Actions
Tags
From astro-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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/astro-check:checkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run `astro check` to get diagnostics for all `.astro` and `.ts` files in the project.
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).npx claudepluginhub ricardo-nth/claude-astro-lsp --plugin astro-checkUse when applying SOLID principles and clean architecture to Astro projects. Enforces files < 100 lines, src/interfaces/ for types, JSDoc on all exports, modular directory structure, and DRY enforcement.
Sets up ast-grep in TypeScript codebases with rules detecting anti-patterns, enforcing best practices, and preventing bugs. Creates sgconfig.yml, rule files, and tests for structural linting, legacy bans, and ratchet gates.
Runs preflight code quality checks (linting, typechecking, tests) by auto-detecting configs in JavaScript/TypeScript, Python, Go, Rust, .NET projects and offers to fix issues.