lint-and-format

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

Updated Nov 17, 2025
One-click install
npx skills add https://github.com/Valynt/ValueOS --skill lint-and-format-valynt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-and-format
Source: https://github.com/Valynt/ValueOS/tree/main/.windsurf/skills/lint-and-format
Command: npx skills add https://github.com/Valynt/ValueOS --skill lint-and-format-valynt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains code quality and consistency by applying linting and formatting standards across the ValueOS monorepo, ensuring shared rules and predictable style.

Core Features & Use Cases

  • Centralized ESLint rules and TypeScript checks for frontend and backend code
  • Unified Prettier formatting including consistent quotes, line widths, and JSX formatting
  • CI/CD integration and pre-commit hooks to catch issues early
  • Applies to new code, code changes, and refactors to enforce standards

Quick Start

Run the lint-and-format skill to enforce code quality across the repository.

Frequently Asked Questions about lint-and-format

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

FAQPage Schema
How do I set up ESLint and Prettier for a TypeScript monorepo?

Setting up ESLint and Prettier for a TypeScript monorepo involves applying centralized linting rules and unified formatting configurations across all packages. This enforces consistent code style, shared rules, and type-checking for both frontend and backend code.

What is the best way to automate code formatting and linting in CI?

The best way to automate code formatting and linting in CI is integrating ESLint, Prettier, and TypeScript checks directly into your CI/CD pipeline. This catches style violations and type errors early before code changes are merged.

Can I use pre-commit hooks to run TypeScript checks and Prettier formatting?

Yes, you can use pre-commit hooks to run TypeScript checks and Prettier formatting. Integrating these tools into pre-commit hooks automatically evaluates code quality and applies consistent formatting locally before changes are committed.

Does linting and formatting work for both frontend and backend code in a monorepo?

Linting and formatting works for both frontend and backend code in a monorepo by using centralized ESLint rules and unified Prettier configurations. This ensures predictable style and shared quality standards across the entire codebase.

Why do I need centralized ESLint rules for my TypeScript monorepo?

You need centralized ESLint rules for your TypeScript monorepo to maintain code quality and consistency. Shared rules enforce predictable style across all packages, preventing configuration drift between different projects.