qlty-check

Code quality checks, formatting, and metrics via qlty CLI

⭐1.3kstars🔀76forks📁View on GitHub🕐Updated Jan 1, 2026

When & Why to Use This Skill

The qlty-check skill is a comprehensive code quality and static analysis tool for Claude agents. It leverages the qlty CLI to provide automated linting, formatting, and code metrics across 40+ programming languages. By integrating over 70 linters into a single interface, it enables developers to identify code smells, calculate cyclomatic complexity, and automatically fix style issues, ensuring high-quality and maintainable codebases throughout the development lifecycle.

Use Cases

  • Automated Code Quality Audits: Quickly scan changed files or entire repositories for linting errors and potential bugs before code handoff or commits.
  • Automated Code Formatting: Maintain consistent coding standards across a team by automatically fixing style and formatting issues with a single command.
  • Technical Debt Assessment: Calculate code metrics such as complexity and duplication to identify 'hotspots' that require refactoring or simplified logic.
  • Multi-Language Project Management: Use a unified tool to manage code quality in polyglot environments, supporting everything from Python and JavaScript to C++ and Go.
nameqlty-check
descriptionCode quality checks, formatting, and metrics via qlty CLI
allowed-tools[Bash, Read]

Qlty Code Quality

Universal code quality tool supporting 70+ linters for 40+ languages via qlty CLI.

When to Use

  • Check code for linting issues before commit/handoff
  • Auto-fix formatting and style issues
  • Calculate code metrics (complexity, duplication)
  • Find code smells

Quick Reference

# Check changed files with auto-fix
uv run python -m runtime.harness scripts/qlty_check.py --fix

# Check all files
uv run python -m runtime.harness scripts/qlty_check.py --all

# Format files
uv run python -m runtime.harness scripts/qlty_check.py --fmt

# Get metrics
uv run python -m runtime.harness scripts/qlty_check.py --metrics

# Find code smells
uv run python -m runtime.harness scripts/qlty_check.py --smells

Parameters

Parameter Description
--check Run linters (default)
--fix Auto-fix issues
--all Process all files, not just changed
--fmt Format files instead
--metrics Calculate code metrics
--smells Find code smells
--paths Specific files/directories
--level Min issue level: note/low/medium/high
--cwd Working directory
--init Initialize qlty in a repo
--plugins List available plugins

Common Workflows

After Implementation

# Auto-fix what's possible, see what remains
uv run python -m runtime.harness scripts/qlty_check.py --fix

Quality Report

# Get metrics for changed code
uv run python -m runtime.harness scripts/qlty_check.py --metrics

# Find complexity hotspots
uv run python -m runtime.harness scripts/qlty_check.py --smells

Initialize in New Repo

uv run python -m runtime.harness scripts/qlty_check.py --init --cwd /path/to/repo

Direct CLI (if qlty installed)

# Check changed files
qlty check

# Auto-fix
qlty check --fix

# JSON output
qlty check --json

# Format
qlty fmt

Requirements

vs Other Tools

Tool Use Case
qlty Unified linting, formatting, metrics for any language
ast-grep Structural code patterns and refactoring
morph Fast text search