How do you monitor code quality? Linters, pre-commit hooks, or something else?

Typically, several tools and practices are used for code quality control:

• Linters (e.g., ESLint for JavaScript/TypeScript) help automatically find and fix style errors and potential bugs.
• Pre-commit hooks (e.g., using Husky) run linters, tests, or formatters before each commit, preventing bad code from entering the repository.
• Formatters (Prettier) ensure a consistent code style.
• Code Review — a mandatory step where colleagues review the code.
• Automated tests (unit, integration) are run in CI/CD to verify functionality.

Example of setting up a pre-commit hook with Husky and ESLint:

// package.json
{
  "husky": {
    "hooks": {
      "pre-commit": "eslint . --fix"
    }
  }
}

This guarantees that before committing, the code is automatically checked and fixed according to ESLint rules.