skills.rest
minh2004pd
minh2004pdCOMMUNITY
Explore all skills by this author →
GitHub

verify-fe

Run TypeScript type-checking, ESLint linting, and a Vite production build.

18|6|Updated Apr 1, 2026
Search Tags:#frontend#build#eslint#vite#types#lint#ci
One-click install
npx skills add https://github.com/minh2004pd/chatbotfullpipeline --skill verify-fe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-fe
Source: https://github.com/minh2004pd/chatbotfullpipeline/tree/main/.claude/skills/verify-fe
Command: npx skills add https://github.com/minh2004pd/chatbotfullpipeline --skill verify-fe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams prevent broken frontend code by automatically running TypeScript type-checking, ESLint linting, and a production build from the frontend/ directory before commits or deployments.

Core Features & Use Cases

  • Type-checking: Verifies TypeScript types to catch errors ESLint might miss.
  • Linting: Enforces coding standards with ESLint and reports all violations.
  • Build validation: Executes a full tsc and vite build to catch import, env, and bundling issues during production prep.
  • Use Case: Pre-merge checks in CI pipelines or local pre-commit hooks to guarantee deploy-ready frontend code.

Quick Start

From the frontend/ directory, run type-check, lint, and build in order and report the first failure, or success if all pass.

Frequently Asked Questions about verify-fe

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

FAQPage Schema
How do I run TypeScript type-checking, ESLint, and Vite build checks before deploying my frontend?▼

To run frontend checks before deploying, execute TypeScript type-checking, ESLint linting, and a full Vite production build in sequence from the frontend directory, reporting the first failure encountered or a success message if all pass.

Why should I validate TypeScript types and run a Vite build before committing frontend code?▼

Validating TypeScript types and running a Vite build before committing catches import, environment, and bundling issues early, ensuring frontend code integrity and preventing broken deployments by verifying style rules and production build success.

Can I use this to check frontend code health in a CI/CD pipeline?▼

Yes, you can use this to check frontend code health in a CI/CD pipeline or local pre-commit hooks, validating a frontend directory's integrity across TypeScript types, ESLint style rules, and Vite build success before merges or releases.

What is the best way to catch ESLint violations and TypeScript errors before a frontend release?▼

The best way to catch ESLint violations and TypeScript errors before a frontend release is to run automated type-checking, linting, and a full Vite production build, which identifies the first failure to guarantee deploy-ready code.

Does the build validation process stop at the first error when checking frontend integrity?▼

Yes, the frontend integrity validation process runs type-check, lint, and build checks in order and stops at the first failure, providing a success message only when TypeScript types, ESLint, and Vite build all pass without errors.

Related Skills

Explore More Software Engineering Skills→
martimramosmartimramos
1

forge-lang-typescript

Standardize TypeScript projects with type checks, Jest or Vitest tests, ESLint, and Prettier.

Community
Intermediate
Pravin-surawasePravin-surawase
5

react-validation

Run build, lint, type-check, and test checks on React frontend changes.

Community
Intermediate
ValyntValynt

lint-and-format

Automate ESLint, Prettier, and type-checking across a TypeScript monorepo.

Official
Advanced
Marshall-HallenbeckMarshall-Hallenbeck
5

lint

Automate formatting, linting, and type checking for Python, JavaScript, TypeScript, and Bash projects.

Community
Intermediate