code-quality

Run ESLint, Prettier, and TypeScript checks via Husky git hooks.

2|1|Updated Nov 24, 2025
One-click install
npx skills add https://github.com/ToonVos/empty-opensaas --skill code-quality-toonvos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/ToonVos/empty-opensaas/tree/main/.claude/skills/code-quality
Command: npx skills add https://github.com/ToonVos/empty-opensaas --skill code-quality-toonvos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires eslint, prettier, typescript, husky, lint-staged.

What problem does it solve?

This Skill establishes a comprehensive code quality workflow, automating checks for linting, formatting, and type safety before every commit and push. It ensures consistent code style, prevents common errors, and maintains a high standard of code health across the project.

Core Features & Use Cases

  • Automated Git Hooks: Integrates Husky to run ESLint, Prettier, and TypeScript checks automatically on git commit and git push.
  • 2-Tier Type Safety: Defines strict type safety standards for production code and a pragmatic approach for tests/mocks, balancing rigor with practicality.
  • Comprehensive Error Resolution: Provides detailed diagnostic steps and fixes for common type errors, linting issues, and hook failures, streamlining the debugging process.
  • Use Case: Before creating a pull request, use this Skill to automatically format your code with Prettier, fix ESLint issues, and verify TypeScript types. This ensures your code adheres to project standards and passes CI checks on the first try.

Quick Start

Run all code quality checks (Prettier, ESLint, TypeScript) on the entire codebase. Auto-fix any formatting or linting issues found.

Frequently Asked Questions about code-quality

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

FAQPage Schema
How do I automate code quality checks before committing code?

Automate code quality checks using git hooks with Husky to run ESLint, Prettier, and TypeScript validation automatically on commit and push. This prevents issues from entering your repository and ensures all code meets project standards before review.

Can I enforce both linting and formatting standards in my TypeScript project?

Yes. ESLint handles linting to catch errors and code-style violations, while Prettier auto-formats code for consistency. Run both together in pre-commit hooks to enforce standards across your entire TypeScript codebase automatically.

What's the best way to fix ESLint and formatting issues before pushing code?

Configure Husky hooks to run ESLint and Prettier with auto-fix flags on pre-commit and pre-push stages. This resolves fixable issues automatically, reducing manual effort and ensuring code passes CI checks on first submission.

How do I set different type-checking strictness for production and test code?

Implement a 2-tier TypeScript configuration: strict mode for production code to catch type errors early, and pragmatic mode for tests and mocks to balance rigor with test-writing practicality without sacrificing safety.

Do I need to run quality checks manually or can they run automatically?

Checks run automatically via Husky git hooks on commit and push—no manual step required. The workflow integrates into your development pipeline so code validation happens transparently before each git operation.

What dependencies do I need to set up code quality automation?

You need ESLint for linting, Prettier for formatting, TypeScript for type checking, Husky to manage git hooks, and lint-staged to run checks only on changed files. Together they create an end-to-end automated quality workflow.