lint

Lint

Run configured linters across the full project. Includes whole-project-only linters (brakeman, clippy) that don't run in the PostToolUse hook.

Usage

• /lint — Run all enabled linters on the full project
• /lint ruby — Run only Ruby linters
• /lint reek — Run only the reek linter
• /lint semgrep — Run only Semgrep (tool linter)
• /lint --fix — Run autofix on all files first, then lint

Arguments after /lint are parsed as:

• A language name (ruby, javascript, python, go, rust, markdown, html, shell) → filter to that language
• A linter name (rubocop, reek, eslint, ruff, etc.) → filter to that specific linter
• A tool linter name (semgrep) → filter to that tool linter
• --fix → run autofix commands before linting

Step 1: Load Config

PROJECT_DIR="${CLAUDE_PROJECT_DIR:-$(pwd)}"
PROJECT_HASH=$(echo "$PROJECT_DIR" | tr '/' '-' | sed 's/^-//')
CONFIG_FILE="$HOME/.claude/code-lint/$PROJECT_HASH/config.json"

If no config exists, tell the user to run /setup-lint first.

Read and parse the config JSON.

Step 2: Determine Scope

Parse arguments to determine what to run:

• No args → all enabled languages, all enabled linters
• Language arg → only that language's linters
• Linter arg → only that specific linter
• --fix → enable autofix mode

Step 3: Run Linters

For each enabled linter in scope:

Single-file linters

Find all matching files (using file_patterns), excluding paths that match exclude_patterns. Run the linter on all matching files at once (most linters accept multiple files or directories).

cd "$PROJECT_DIR"

# If --fix mode, run autofix first
bundle exec rubocop -A --fail-level=error .

# Then run the lint check
bundle exec rubocop .

Whole-project-only linters

Run these against the project root:

cd "$PROJECT_DIR"
bundle exec brakeman -q
cargo clippy -- -D warnings

Tool linters (e.g. Semgrep)

After running per-language linters, check the tool_linters section of the config. For each enabled tool linter: