skills.rest
monam2
monam2COMMUNITY
Explore all skills by this author →
GitHub

Lint & TypeCheck

Run ESLint and TypeScript checks to identify code quality issues.

Updated Jan 18, 2026
Search Tags:#typescript#eslint#nextjs#code-quality#static-analysis#lint#typecheck
One-click install
npx skills add https://github.com/monam2/traders --skill lint-typecheck-monam2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Lint & TypeCheck
Source: https://github.com/monam2/traders/tree/main/.agent/skills/lint-typecheck
Command: npx skills add https://github.com/monam2/traders --skill lint-typecheck-monam2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ESLint and TypeScript static analysis to help teams catch code quality and type-safety issues early, reducing bugs in production.

Core Features & Use Cases

  • Linting with ESLint to catch stylistic and programming errors and enforce code standards.
  • Type checking with TypeScript to ensure type safety across the codebase.
  • CI integration and local development support for Next.js and TypeScript projects.

Quick Start

Run the lint workflow to identify and fix issues across the codebase.

Frequently Asked Questions about Lint & TypeCheck

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

FAQPage Schema
How do I run ESLint and TypeScript type checking in a Next.js project?▼

Run ESLint and TypeScript type checking in a Next.js project by applying a recommended config that extends next/core-web-vitals, next/typescript, and prettier, executing TypeScript with noEmit to catch type errors early.

What ESLint rules are enforced for TypeScript static analysis?▼

TypeScript static analysis enforces rules like no-unused-vars and no-explicit-any to catch code quality issues, ensure type safety, and reduce bugs in production across JavaScript and TypeScript projects.

Can I integrate lint and type checks into CI pipelines for local development?▼

Yes, you can integrate lint and type checks into CI pipelines and local development across Next.js and TypeScript projects to catch lint errors and type errors early before deployment.

What is the best way to catch code quality issues with ESLint and TypeScript noEmit?▼

The best way to catch code quality issues is using ESLint for stylistic errors and TypeScript with noEmit for type safety, applying a recommended config that extends next/core-web-vitals and prettier.

Does this static analysis approach work with Prettier formatting rules?▼

Yes, static analysis works with Prettier formatting rules by extending the prettier config within ESLint, ensuring code standards are enforced alongside type checks without conflicting formatting errors.

Related Skills

Explore More Software Engineering Skills→
KikolatorKikolator

scaffold

Generate boilerplate scaffolds by inferring project conventions from existing code.

Community
Intermediate
EotelEotel

verify

Orchestrate build, type, lint, test, console log, and git status checks.

Community
Intermediate
caseymanoscaseymanos

git-hooks

Configure Husky Git hooks for pre-commit linting, pre-push testing, and commit message validation.

Community
Advanced
aniruddh2003aniruddh2003
1

speckit.checker

Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.

Community
Intermediate