mcpField
Q
qlty-check

qlty-check

github.com/parcadeiTesting & quality3.9k486 installsUpdated 39w ago
Repository

About qlty-check

qlty-check is a skill for running code-quality checks through the qlty CLI. It is aimed at developers who need linting, formatting, and metrics across changed files or an entire repository, including automatic fixes and code-smell detection.

Key features

  1. 01Run linters and automatically fix issues
  2. 02Format code
  3. 03Calculate complexity and duplication metrics
  4. 04Find code smells
  5. 05Target paths and set issue levels

Use cases

  1. 01Check changed code before commit or handoff
  2. 02Automatically fix style and formatting issues
  3. 03Assess complexity and locate code smells

MCP support

The project mentions `servers/qlty/server.py` as a wrapper around the qlty CLI for MCP clients.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/parcadei/continuous-claude-v3 --skill qlty-check

After installing, type/qlty-checkin Claude Code to confirm it loaded.

Details

From the project README

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

ParameterDescription
--checkRun linters (default)
--fixAuto-fix issues
--allProcess all files, not just changed
--fmtFormat files instead
--metricsCalculate code metrics
--smellsFind code smells
--pathsSpecific files/directories
--levelMin issue level: note/low/medium/high
--cwdWorking directory
--initInitialize qlty in a repo
--pluginsList 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

ToolUse Case
qltyUnified linting, formatting, metrics for any language
ast-grepStructural code patterns and refactoring
morphFast text search

Comments

Markdown supported