lint-runner

Detect project linters and run their commands across Go, TypeScript, Python, and Rust.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/RaNDoM6913/claude-code-superkit --skill lint-runner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-runner
Source: https://github.com/RaNDoM6913/claude-code-superkit/tree/main/packages/codex/skills/lint-runner
Command: npx skills add https://github.com/RaNDoM6913/claude-code-superkit --skill lint-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically detects and runs the appropriate linters for a multi-language project, ensuring code quality across a repo.

Core Features & Use Cases

  • Detects linters by inspecting common config files (go.mod, package.json, pyproject.toml, Cargo.toml, Makefile targets) and runs corresponding commands.
  • Supports backend, frontend, or all scopes, and can operate in auto-fix mode when requested.
  • Generates per-linter reports and a consolidated summary of results for quick triage.

Quick Start

Tell me the project path and scope (backend, frontend, or all) and I will auto-detect configured linters, run them, and summarize results.

Frequently Asked Questions about lint-runner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run linters across a multi-language monorepo with Go, TypeScript, Python, and Rust?

Run linters across a multi-language monorepo by detecting common config files like go.mod, package.json, pyproject.toml, and Cargo.toml. The tool inspects these files to identify and execute the corresponding lint commands for each language automatically.

What is the best way to auto-detect and run project linters for backend and frontend codebases?

Auto-detecting project linters for backend and frontend codebases involves scanning for common configuration files and Makefile lint targets. This approach ensures the appropriate lint commands are executed across different scopes without manual configuration.

Does the linter auto-fix mode work with existing Makefile targets?

Linter auto-fix mode works with existing Makefile targets by preferring them when present. It detects the targets alongside common config files and applies fixes automatically across the specified backend, frontend, or all scopes.

How do I get a consolidated summary of lint results for a multi-language project?

Get a consolidated summary of lint results by running the auto-detection tool across your multi-language project. It generates per-linter reports and combines them into a single summary for quick triage of code quality issues.

Do I need a Makefile to run linters for TypeScript and Python projects?

You do not need a Makefile to run linters for TypeScript and Python projects. The tool can detect and run linters using common config files like package.json and pyproject.toml, but it will prefer Makefile lint targets if they are present.

Can I scope linting to only the backend or frontend codebase?

You can scope linting to only the backend or frontend codebase by specifying the desired scope. The tool will auto-detect configured linters within that specific scope and run them, providing a targeted summary of results.