eslint-audit

To audit ESLint configs across a multi-package TypeScript project, run an audit on your repository to identify misconfigurations and rule gaps. It analyzes base configs and per-package overrides to generate a recommended rule set and report.

Enforcing consistent lint rules in a monorepo requires auditing base ESLint configurations and per-package overrides. Applying shared config architectures across multiple packages ensures consistent linting standards and reduces rework.

You can integrate oxlint with your existing ESLint setup. The audit process includes integrating oxlint and providing agent-specific lint guidance across packages to enforce standards and identify configuration gaps.

Creating custom ESLint rules for shared configs involves authoring specific rules and applying shareable configurations across your project. The audit guides this process to ensure packages enforce consistent linting practices.

Yes, this ESLint audit works with per-package override patterns. It explicitly satisfies base and per-package config patterns, identifying misconfigurations and providing actionable guidance for agents across all packages.