setup-linting — Claude Code command: linters and code quality
Sets up linters and quality checks in your project: ESLint, Flake8, Pylint, MyPy, Clippy. Useful when style rules need to be enforced automatically.
npx claude-code-templates@latest --command setup/setup-lintingWhat setup-linting does
The command starts by inspecting the project: it looks for .js, .ts, .py, .rs files, checks for configs like .eslintrc.*, pyproject.toml or tslint.json, reads the package manager from package.json, requirements.txt or Cargo.toml, and counts which linters are already installed. Then it installs and configures tools for the language you picked.
The argument sets the focus: --javascript, --typescript, --python, --multi-language, or a plain language name. It writes style and error-detection rules, wires the linter into your IDE, adds checks to pre-commit and CI, and can define custom rules for your architecture. Tools it uses: Read, Write, Edit, Bash.
One caveat: without a language argument the command relies on whatever it detects in the repo. If the project mixes several languages and you skip the flag, expect a scattered result — say up front what you want configured.
What it helps with
- install ESLint and connect it to the editor
- add code checks to pre-commit and CI
- configure linters for several languages in one repo
- define custom rules for project architecture
- find already installed linters and avoid duplicates
Example prompts for the agent
- /setup-linting --typescript
- /setup-linting --python
- /setup-linting --multi-language
How to install setup-linting
1claude-code-templates
npx claude-code-templates@latest --command setup/setup-linting2Manually: put the files in place
.claude/commands/setup-linting.mdCall it with /setup-linting. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/setup-linting.mdCall it with /prompts:setup-linting. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/setup-linting.prompt.mdManually: put the files in place
.gemini/commands/setup-linting.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about setup-linting
How do I install setup-linting in Claude?
Through the templates: run npx claude-code-templates@latest --command setup/setup-linting, then check that the file landed at .claude/commands/setup-linting.md.
What does setup-linting do?
It configures linters and code quality analysis for the language you choose, covering rules, IDE integration and CI checks.
Which languages are supported?
JavaScript, TypeScript and Python via separate flags, plus a --multi-language mode for projects that mix several languages.
Source text
setup-linting.md · MIT
--- allowed-tools: Read, Write, Edit, Bash argument-hint: "[language] | --javascript | --typescript | --python | --multi-language" description: Configure comprehensive code linting and quality analysis tools with automated enforcement --- # Setup Code Linting Configure comprehensive code linting and quality analysis: **$ARGUMENTS** ## Current Code Quality State - Languages detected: !`find . -name "*.js" -o -name "*.ts" -o -name "*.py" -o -name "*.rs" | head -5` - Existing linters: @.eslintrc.* or @pyproject.toml or @tslint.json - Package manager: @package.json or @requirements.txt or @Cargo.toml - Code quality tools: !`which eslint flake8 pylint mypy clippy 2>/dev/null | wc -l` ## Task Setup comprehensive code linting system with quality analysis and automated enforcement: **Language Focus**: Use $ARGUMENTS to configure JavaScript/TypeScript ESLint, Python linting, or multi-language quality analysis **Linting Configuration**: 1. **Tool Installation** - ESLint, Flake8, Pylint, MyPy, Clippy, language-specific linters and plugins 2. **Rule Configuration** - Code style rules, error detection, best practices, security patterns, performance guidelines 3. **IDE Integration** - Real-time linting, error highlighting, quick fixes, workspace settings 4. **Quality Gates** - Pre-commit validation, CI/CD integration, pull request checks, quality metrics 5. **Custom Rules** - Project-specific patterns, architectural constraints, team conventions 6. **Performance** - Incremental linting, caching strategies, parallel execution, optimization **Advanced Features**: Security linting, accessibility checks, performance analysis, dependency analysis, code complexity metrics. **Team Standards**: Shared configurations, style guides, review guidelines, onboarding documentation. **Output**: Complete linting system with automated quality gates, team standards enforcement, and comprehensive code analysis.
© davila7 · MIT · davila7/claude-code-templates
