How do I install the Qlty Check skill?

Run npx skillmds@latest add parcadei/qlty-check in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Qlty Check skill do?

Code quality checks, formatting, and metrics via qlty CLI It is listed under Coding & Dev Tools on SkillMD.

Is Qlty Check safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Qlty Check?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Qlty Check free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Qlty Check?

parcadei (@parcadei) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Qlty Check by parcadei — Agent Skill

Name: Qlty Check
Rating: 4.5 (4 reviews)
Author: parcadei

File contents

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

qlty CLI: https://github.com/qltysh/qlty
MCP server: servers/qlty/server.py wraps CLI
Config: .qlty/qlty.toml in repo (run qlty init first)

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

Source: parcadei/Continuous-Claude-v3 → .claude/skills/qlty-check/SKILL.md

---name: qlty-checkdescription: Code quality checks, formatting, and metrics via qlty CLI--- # 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 ```bash # 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 ```bash # Auto-fix what's possible, see what remains uv run python -m runtime.harness scripts/qlty_check.py --fix ``` ### Quality Report ```bash # 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 ```bash uv run python -m runtime.harness scripts/qlty_check.py --init --cwd /path/to/repo ``` ## Direct CLI (if qlty installed) ```bash # Check changed files qlty check # Auto-fix qlty check --fix # JSON output qlty check --json # Format qlty fmt ``` ## Requirements - **qlty CLI**: https://github.com/qltysh/qlty - **MCP server**: `servers/qlty/server.py` wraps CLI - **Config**: `.qlty/qlty.toml` in repo (run `qlty init` first) ## 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 | --- **Source:** [`parcadei/Continuous-Claude-v3`](https://github.com/parcadei/Continuous-Claude-v3) → `.claude/skills/qlty-check/SKILL.md`

Frequently asked questions

Qlty Check