qlty-check

Run automated code quality checks and metrics with the qlty CLI.

8|1|Updated Jan 4, 2026

Search Tags:#code quality #developer tools #linting #formatting #code metrics #qlty

Ready to run

npx skills add https://github.com/scooter-lacroix/Maestro --skill qlty-check-scooter-lacroix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qlty-check
Source: https://github.com/scooter-lacroix/Maestro/tree/main/maestro/skills/quality/qlty-check
Command: npx skills add https://github.com/scooter-lacroix/Maestro --skill qlty-check-scooter-lacroix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of checking code for linting issues, formatting errors, and code smells, ensuring a high standard of code quality across various languages.

Core Features & Use Cases

Linting and Formatting: Automatically checks and fixes code style and potential errors using the qlty CLI.
Code Metrics: Calculates metrics like complexity and duplication to identify areas for improvement.
Use Case: Before committing code, run this Skill to automatically format your files and identify any critical linting errors, preventing common mistakes and maintaining consistency.

Quick Start

Run the qlty-check skill to automatically fix formatting and linting issues in your changed code files.

Frequently Asked Questions about qlty-check

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

FAQPage Schema

How do I automate code quality checks before committing?▼

To automate code quality checks before committing, run this Skill to automatically format files and identify critical linting errors. It uses the qlty CLI to check for bugs and code smells across multiple languages.

What are code metrics and how do they detect code smells?▼

Code metrics like complexity and duplication identify areas for improvement by calculating structural measurements. This Skill uses the qlty CLI to compute these metrics, enabling early detection of code smells across multiple programming languages.

Do I need a configuration file to run qlty for linting and formatting?▼

Yes, you need a `.qlty/qlty.toml` configuration file to define repository-specific settings for the qlty CLI. This file is required to run automated code quality checks, formatting, and metric calculations.

Can I use this to fix formatting errors across multiple programming languages?▼

Yes, you can fix formatting errors across multiple programming languages using this Skill. It leverages the qlty CLI to automatically check and fix code style, ensuring consistency across your repository.

What's the best way to calculate code complexity and duplication?▼

The best way to calculate code complexity and duplication is using this Skill to compute code metrics via the qlty CLI. It identifies areas for improvement by measuring structural properties to maintain high code standards.

Why does my code quality check require the qlty CLI?▼

Your code quality check requires the qlty CLI because it is the underlying engine this Skill uses to perform linting, formatting, and metric calculations. Without it, the automated checks for bugs and code smells cannot run.