About lint
A project linting skill that detects the repository’s existing linter or formatter, runs its check, and reports errors with file and line references. It avoids assuming a toolchain and only applies fixes when requested.
Key features
- 01Detects project-defined lint tasks
- 02Falls back to ecosystem tools
- 03Runs lint checks
- 04Reports errors by file and line
- 05Applies fixes only on request
Use cases
- 01Check code style before a change is merged
- 02Identify lint errors in an unfamiliar repository
- 03Fix lint issues when explicitly requested
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/lintin Claude Code to confirm it loaded.
Details
From the project READMELinting
Run the project's linter/formatter — detect it, don't assume a toolchain.
Detection
Prefer a task the project already defines, then fall back to the ecosystem tool:
| Ecosystem | Check | Fix |
|---|---|---|
| Node | package.json lint (eslint/biome) | lint:fix |
| Python | ruff check / flake8 | ruff check --fix |
| Go | golangci-lint run / gofmt -l | gofmt -w |
| Rust | cargo clippy / cargo fmt --check | cargo fmt |
| else | Makefile / CI lint target | — |
Workflow
- Detect the linter (project task first, then ecosystem default)
- Run the check command
- For fixes: run the fix variant (only when requested)
- Report
file:linereferences for all errors
Rules
- Prefer the project's defined task over a raw tool call
- Never invent a linter the project doesn't use
Error Handling
- If no linter or task found → report which config/task is expected and stop
- If the linter exits with parse errors → report each file-level parse error separately with
file:line - If the linter config is missing → report which config is expected and stop
Comments
Markdown supported