code-check

Run ESLint, TypeScript checks, and build validation for frontend and backend packages.

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/zhu637882-stack/jiaoyi --skill code-check-zhu637882-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-check
Source: https://github.com/zhu637882-stack/jiaoyi/tree/main/qoder-config-backup/skills/code-check
Command: npx skills add https://github.com/zhu637882-stack/jiaoyi --skill code-check-zhu637882-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

代码质量检查任务繁多,需要在前端和后端同时进行静态检查、类型检查和构建测试,以确保代码质量与稳定性。

Core Features & Use Cases

  • ESLint 静态分析前端代码,捕获潜在错误。
  • TypeScript 类型检查,确保类型安全和编译无误。
  • 构建验证,确保产物可构建且无回归。
  • 未使用代码检查,识别冗余变量和导入。
  • 适用于日常代码审查、CI 集成和本地开发快速回归的场景。

Quick Start

Run the frontend and backend quality checks using the commands described to verify code health.

Frequently Asked Questions about code-check

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

FAQPage Schema
How do I automate ESLint and TypeScript checks for both frontend and backend projects?

Automate ESLint and TypeScript checks for frontend and backend projects by running deterministic commands that execute static analysis, type checking, and build validation to ensure code health.

What is the best way to integrate code quality checks into a CI workflow?

Integrate code quality checks into CI workflows using deterministic commands that provide consistent results and clear error reporting for build validation and linting across packages.

Can I run build validation and unused code checks locally before pushing?

Run build validation and unused code checks locally to identify redundant variables and imports, catching potential errors and regressions quickly during everyday development.

Does this code quality automation work without external dependencies?

Code quality automation operates without external dependencies, running ESLint, TypeScript checks, and build validation directly within your typical development workflows.

Why should I run static analysis and build tests for frontend and backend simultaneously?

Running static analysis and build tests for frontend and backend simultaneously ensures type safety, catches potential errors early, and prevents regressions across your entire project.