code-quality-tooling-edho-ferdian

Install ESLint with a flat config (eslint.config.js), add Prettier with eslint-config-prettier placed last in the config array, then run npx husky init and configure lint-staged to run eslint --fix and prettier --write on staged files in the pre-commit hook.

Biome is the recommended default for new projects because one Rust-based tool handles both linting and formatting with no config conflicts. Choose ESLint plus Prettier only when you need plugin coverage Biome lacks, such as eslint-plugin-jsx-a11y, or have a large existing ESLint config.

Pre-commit should run lint and format on staged files only via lint-staged, finishing in under a second. Pre-push should run the type-checker and a fast test subset. CI runs the full test suite and build as the authoritative gate, since local hooks can always be bypassed.

The prepare script added by husky init was not committed, or someone installed with npm install --ignore-scripts. Verify package.json contains "prepare": "husky" and that it is committed so hooks install automatically on every npm install.

For Python, use Ruff for linting and formatting with the pre-commit framework as the hook runner. For Go, use golangci-lint with either the pre-commit framework or lefthook. For polyglot monorepos, lefthook is the recommended single hook runner.

Conflicts over quote style or trailing commas mean eslint-config-prettier is missing or not positioned last in the flat config array. Fix the config ordering rather than disabling individual rules, or switch to Biome where this conflict class cannot occur.