check

Runs backend and frontend verification suites for the kajet-turbo codebase.

1|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/jpalczewski/kajet-turbo --skill check-jpalczewski
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/jpalczewski/kajet-turbo/tree/main/.claude/skills/check
Command: npx skills add https://github.com/jpalczewski/kajet-turbo --skill check-jpalczewski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying a full-stack codebase requires running many separate lint, type-check, and test commands across backend and frontend, and it is easy to skip one or misreport results. This Skill runs the complete verification suite for kajet-turbo and reports every failure with file and line references. ## Core Features & Use Cases - Backend Verification: Runs ruff lint, ruff format check, ty type checking, and pytest via uv. - Frontend Verification: Runs prettier and eslint via bun lint, plus svelte-check in the frontend directory. - Strict Reporting: Never auto-fixes issues and never declares success unless all six checks pass. - Use Case: Before committing a new feature, invoke this Skill to confirm the entire codebase is healthy and get a grouped summary of any failures. ## Quick Start Run the check skill to verify the entire kajet-turbo codebase is healthy before I commit.

Frequently Asked Questions about check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run all lint and test checks before committing?▼

Invoke the check skill from the repo root. It runs ruff check, ruff format check, ty, and pytest for the backend, plus bun lint and svelte-check for the frontend, reporting every failure with file and line.

What tools verify a FastAPI and SvelteKit codebase?▼

This project uses ruff for linting and formatting, ty for type checking, and pytest for backend tests. The frontend uses prettier, eslint, and svelte-check, all orchestrated together by this verification skill.

Does the check skill auto-fix lint errors?▼

No, it is strictly a verification pass and never modifies files. It reports all failures grouped by tool and asks whether you want them fixed afterward.

Why does the check skill report failure when tests pass?▼

All six checks must pass to declare the codebase healthy, including format and type checks. A passing pytest run with a failing ruff format or svelte-check still counts as an unhealthy codebase.

Can backend and frontend checks run in parallel?▼

Yes, the skill instructs running the backend group (ruff, ty, pytest) and frontend group (lint, svelte-check) in parallel where possible, since they operate on separate parts of the repository.