lint-check — Claude Code command: what it does, how to install
lint-check runs the linters your project already configures, sorts findings by severity and can auto-fix style. Useful right before a commit instead of waiting for CI.
MIT ★ 1,424 updated 2026-10-06
.claude/commands/lint-check.mdWhat lint-check does
Four steps. The command first hunts for linter config files: eslint.config.* or .eslintrc* for JS and TS, pyproject.toml, .ruff.toml or setup.cfg for Python, .golangci.yml for Go, rustfmt.toml for Rust. Whatever turns up decides the toolset for the next step: ESLint with Prettier, ruff (or flake8) with black and mypy, golangci-lint with gofmt and go vet, clippy with cargo fmt.
Every finding lands in one of three buckets. Critical means a real defect or a hole: bad types, null dereferences, injection patterns. Warnings cover unused imports, missing return types, naming drift. Style is formatting, import order, trailing spaces, line length. Only style gets an automatic fix through --fix or --write. Type errors and possible nulls you sort out yourself.
The report opens with a PASS, FAIL or WARNINGS verdict, then counts, then file:line for each item and a closing note about committing. It ships inside the project-starter plugin, so you call it as /project-starter:lint-check. Which checks actually run depends on the configs sitting in your repo.
What it helps with
- run every configured linter with one call
- separate blocking defects from cosmetic noise
- auto-fix formatting and import order
- get file and line for each finding
- decide whether a branch is safe to commit
Example prompts for the agent
- Run
/project-starter:lint-checkacross the repo and show me only the critical findings. - Run
/project-starter:lint-check, then apply the style auto-fix and list what changed. - Is this branch ready to commit? Run
/project-starter:lint-checkand tell me.
How to install lint-check
Manually: put the files in place
.claude/commands/lint-check.mdCall it with /lint-check. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/lint-check.mdCall it with /prompts:lint-check. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/lint-check.prompt.mdManually: put the files in place
.gemini/commands/lint-check.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about lint-check
How do I install lint-check in Claude Code?
Copy the command file to .claude/commands/lint-check.md. Inside the project-starter plugin it runs as /project-starter:lint-check.
What does lint-check do?
It finds your linter configs, runs the matching tools and groups the output into critical issues, warnings and style problems. The final report gives a verdict plus files and line numbers.
Which linters does it run?
ESLint and Prettier for JS and TS, ruff or flake8 with black and mypy for Python, golangci-lint, gofmt and go vet for Go, clippy and cargo fmt for Rust.
Source text
lint-check.md · MIT
--- description: Runs linting and code quality checks. Catches style issues, potential bugs, and enforces project standards. --- # Lint Check Run linting and code quality checks. Catches issues before they reach CI. ## Phase 1: Detect Linting Tools Find project's linting configuration: ```bash # JavaScript/TypeScript ls .eslintrc* eslint.config.* .prettierrc* 2>/dev/null # Python ls pyproject.toml .flake8 .ruff.toml setup.cfg 2>/dev/null # Go ls .golangci.yml .golangci.yaml 2>/dev/null # Rust ls rustfmt.toml .rustfmt.toml clippy.toml 2>/dev/null ``` ## Phase 2: Run Linters ### JavaScript/TypeScript ```bash npx eslint . --ext .js,.ts,.tsx --format stylish npx prettier --check . ``` ### Python ```bash ruff check . # or fallback flake8 . black --check . mypy . ``` ### Go ```bash golangci-lint run gofmt -l . go vet ./... ``` ### Rust ```bash cargo clippy -- -D warnings cargo fmt --check ``` ## Phase 3: Categorize Issues ### Critical (Must Fix) - Security vulnerabilities - Undefined variables - Type errors - Potential null pointer issues - SQL injection patterns ### Warnings (Should Fix) - Unused variables/imports - Missing return types - Inconsistent naming - Complex expressions ### Style (Auto-fixable) - Formatting issues - Import ordering - Trailing whitespace - Line length ## Phase 4: Auto-Fix Option Offer to auto-fix style issues: ```bash # JavaScript/TypeScript npx eslint . --fix npx prettier --write . # Python ruff check . --fix black . isort . # Go gofmt -w . # Rust cargo fmt ``` ## Output Format ``` ## Lint Results: [PASS/FAIL/WARNINGS] ### Summary - Errors: X - Warnings: Y - Auto-fixable: Z ### Critical Issues (Must Fix) 1. **[Rule]** - `file:line` - Message: [linter message] - Fix: [how to fix] ### Warnings (Should Fix) 1. **[Rule]** - `file:line` - Message: [message] ### Auto-Fixed (if --fix was run) - [List of auto-fixed issues] ### Commands Used - [List all linting commands run] ### Recommendation [ ] Ready to commit [ ] Fix critical issues first [ ] Run auto-fix and review changes ``` ## Usage This command ships with the project-starter plugin. Invoke with: `/project-starter:lint-check`
© CloudAI-X · MIT · CloudAI-X/claude-workflow-v2