linting-audit

Run /linting-audit at the repository root of a TypeScript project. It reads your eslint.config file, package.json, source files, and CI workflows, then reports findings across four layers and offers to generate an implementation plan.

Yes, the audit auto-detects ESLint or Biome from package.json and configuration files, then dispatches to linter-specific checks. Having both installed is itself reported as a configuration-shape violation.

quality-gates-audit checks whether linting runs at pre-commit, pre-push, and CI stages, which is a lifecycle question. linting-audit checks whether the lint configuration itself is well-formed, covering rule coverage, strictness, and suppression hygiene.

No, the audit is fully read-only and never invokes any linter with --fix or other mutating flags. It only writes report files under .architect-audits/linting-audit and optionally generates a descriptive implementation plan.

The audit continues, marking the linter-foundation check as missing and linter-dependent checks as not-evaluated, while still evaluating independent suppression and CI checks. It recommends installing ESLint or Biome and running quality-gates-audit.

This happens when the lint command fails to start, for example due to a missing binary or invalid configuration. The static analysis still completes, and the findings record a recovery hint to run /preflight --audit=linting --install before retrying.