qlty-check

Code quality checks analyze your entire codebase using 70+ integrated linters and formatters across languages. qlty-check provides a unified interface to run linting, auto-formatting, and metrics gathering in one command, supporting multi-language repos through a single .qlty/qlty.toml configuration file.

Yes. The --fix flag auto-corrects formatting violations and applies lint auto-fixes across your repository. Combined with --fmt, it handles formatting changes while --check mode reports violations without modifying files, making it suitable for pre-commit checks and CI pipelines.

Code quality checks detect code smells using the --smells flag and compute code metrics with --metrics, surfacing issues like complexity, duplication, and maintainability problems. These insights enable quality dashboards and help identify technical debt across multi-language codebases.

qlty-check supports continuous integration pipelines through the qlty CLI and MCP server wrapper configured at .qlty/qlty.toml. Use --check mode in CI to fail builds on violations, --all to scan the entire repo, and optional --level to enforce severity thresholds before deployment.

Yes. qlty-check wraps 70+ existing linters and formatters, working with your repository's established tooling and configurations. The --plugins flag allows selective tool inclusion, and --paths targets specific files, adapting to diverse tech stacks without replacing existing tools.

The --all flag scans your entire repository for comprehensive quality reports, while omitting it or using --paths runs checks on changed files, reducing CI time. Both modes support --fix for auto-corrections, enabling fast pre-commit checks and thorough quality dashboards.