Lint Doctor

Diagnose project environment and configure linting with universal best practices (Google style fallback).

Workflow

1. Detect Environment

Scan project root for config files:

Files Found	Stack Detected
`package.json`, `tsconfig.json`	JS/TS
`package.json` + react in deps	React
`angular.json`	Angular
`vite.config.ts` + vue	Vue
`pyproject.toml`, `setup.py`, `requirements.txt`	Python
`pom.xml`, `build.gradle`	Java
`Cargo.toml`	Rust
`go.mod`	Go

For monorepos: check for workspaces in package.json, multiple config files in subdirectories.

2. User Interaction

Ask initial question using AskUserQuestion:

code

header: "Mode"
question: "How should I configure linting?"
options:
  - label: "Automatic (Recommended)"
    description: "Apply best practices with sensible defaults"
  - label: "Interactive"
    description: "Ask about each configuration choice"

If Interactive, also ask:

code

header: "Strictness"
question: "What strictness level?"
options:
  - label: "Moderate (Recommended)"
    description: "Warnings for style, errors for bugs"
  - label: "Relaxed"
    description: "Mostly warnings, fewer rules"
  - label: "Strict"
    description: "More rules, errors for style violations"

code

header: "Pre-commit"
question: "Set up pre-commit hooks?"
options:
  - label: "No (Recommended)"
    description: "Just configure the linter"
  - label: "Yes"
    description: "Add husky + lint-staged for JS, or pre-commit for Python"

3. Configure

Based on detected stack, apply rules from the appropriate reference:

•JavaScript/TypeScript/React/Vue/Angular: See references/javascript.md
•Python: See references/python.md
•Java: See references/java.md
•Rust: See references/rust.md
•Go: See references/go.md
•Pre-commit hooks: See references/pre-commit.md

Priority: Enhance existing configs. Only create new files if none exist.

4. Output

•Show changes - Display diff of config modifications
•List dependencies - Show packages to install
•Ask to install - Use AskUserQuestion to confirm installation
•Ask about --fix - Offer to run auto-fix after setup

code

header: "Install"
question: "Install these dependencies?"
options:
  - label: "Yes (Recommended)"
    description: "Run npm install / pip install now"
  - label: "No"
    description: "I'll install manually"

code

header: "Auto-fix"
question: "Run auto-fix on existing code?"
options:
  - label: "Yes"
    description: "Run linter with --fix flag"
  - label: "No (Recommended)"
    description: "Just configure, don't modify code yet"

Severity Guidelines

Follow best practice conventions:

Category	Severity	Examples
Bugs	`error`	no-undef, no-unused-vars
Security	`error`	no-eval, no-implied-eval
Complexity	`warn`	cognitive-complexity, max-depth
Style	`warn`	prefer-const, no-var
Formatting	`off`	Let Prettier handle it