qlty-check

You can automate code quality checks before merging by running a CLI tool to surface issues, apply formatting fixes, and generate a quality report. This streamlines review cycles and enforces standards across your software repositories.

Yes, you can run centralized static analysis and linting across multiple languages. The CLI applies automated checks to software repositories to enforce style and quality regardless of the language used.

To auto-fix formatting issues and generate metrics, use the CLI to run checks with the auto-fix and metrics options. This automatically fixes eligible issues and identifies risk hotspots in your code.

Yes, you need the qlty CLI installed to use these automated code quality checks. The skill relies on the CLI to perform static analysis, formatting, and metrics generation across your repositories.

The best way to run a full code quality scan and output a JSON report is by executing a full scan command with the JSON flag. This performs a comprehensive check across all files and returns structured data.

Yes, you can use code quality automation for pre-commit checks and CI pipelines. The CLI is designed to integrate into these workflows, enforcing standards and surfacing issues before code is merged.