Local Validation

Run TypeScript type checking, ESLint linting, Prettier formatting, and Jest tests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Coverage-Creatives/zeus --skill local-validation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Local Validation
Source: https://github.com/Coverage-Creatives/zeus/tree/main/.windsurf/local-validation
Command: npx skills add https://github.com/Coverage-Creatives/zeus --skill local-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires concurrently, npm-run-all, cross-env, @next/bundle-analyzer, webpack-bundle-analyzer, eslint-plugin-json, eslint-plugin-yaml, eslint-plugin-markdown, @testing-library/jest-dom, @testing-library/user-event, husky, lint-staged, onchange, rimraf, jest, and includes scripts (resource) components.

What problem does it solve?

This Skill establishes a robust local validation process to catch code quality issues, bugs, and performance regressions early in the development cycle, preventing them from reaching production.

Core Features & Use Cases

  • Automated Checks: Integrates TypeScript type checking, ESLint linting, Prettier formatting, and Jest testing.
  • Pre-Commit & Pre-Push Hooks: Enforces code standards automatically before commits and pushes.
  • CI Integration: Provides scripts for seamless integration into Continuous Integration pipelines.
  • Use Case: Before committing code, run npm run validate:quick to ensure your code is well-formatted, type-safe, and passes basic tests, saving you from potential merge conflicts and CI failures.

Quick Start

Run npm run validate:quick to perform a quick validation of your code.

Frequently Asked Questions about Local Validation

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

FAQPage Schema
How do I set up pre-commit hooks for TypeScript, ESLint, and Jest?▼

Pre-commit hooks automate TypeScript type checking, ESLint linting, Prettier formatting, and Jest testing by validating code locally before commits are finalized. This automated gate prevents code quality issues from reaching the repository.

What is the best way to run local code validation before pushing to CI?▼

Running local code validation via a quick validation script checks formatting, type safety, and tests before pushing. This catches bugs and performance regressions early, saving you from potential merge conflicts and CI pipeline failures.

Can I use lint-staged and husky to automate Prettier formatting?▼

Yes, lint-staged and husky integrate to automate Prettier formatting against staged files. This combination enforces code standards automatically during the pre-commit phase, ensuring consistent formatting without manual intervention.

Does local validation support watch modes for continuous development feedback?▼

Local validation supports watch modes using onchange to provide continuous development feedback loops. This allows developers to run automated checks dynamically as files change, streamlining the local testing and linting experience.

How do I add CI-ready scripts for continuous integration pipelines?▼

CI-ready scripts integrate TypeScript checking, ESLint, and Jest into continuous integration pipelines. These scripts standardize the automated validation sequence, ensuring code meets quality gates before deployment in CI environments.

Why should I run a quick validation script before committing code?▼

Running a quick validation script before committing ensures your code is well-formatted, type-safe, and passes basic tests. This early local check prevents low-quality code from entering the repository and failing remote CI builds.