Qlty Check
- 466 installs
- 3.9k repo stars
- Updated January 26, 2026
- parcadei/continuous-claude-v3
qlty-check is a Claude skill that runs linting, auto-fix formatting, and code metrics across changed files via the qlty CLI for developers who need pre-commit quality gates supporting 70+ linters and 40+ languages.
About
qlty-check is a parcadei continuous-claude-v3 skill that wraps the qlty CLI for universal code quality checks across 70+ linters and 40+ languages. Agents invoke harness scripts to lint changed files with optional auto-fix, format code, or calculate complexity and duplication metrics before commit or handoff. Commands support checking only diffs, scanning all files, or running format-only passes. Developers reach for qlty-check when they want a single quality tool covering many languages instead of configuring separate ESLint, Prettier, and language-specific linters manually.
- qlty-check
Qlty Check by the numbers
- 466 all-time installs (skills.sh)
- +2 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #905 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/parcadei/continuous-claude-v3 --skill qlty-checkAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 466 |
|---|---|
| repo stars | ★ 3.9k |
| Last updated | January 26, 2026 |
| Repository | parcadei/continuous-claude-v3 ↗ |
How do you lint 40+ languages with one CLI?
Use qlty-check for development tasks
Who is it for?
Developers needing unified lint, format, and metrics across polyglot codebases before commit or agent handoff.
Skip if: Projects already locked to a single-language linter stack with no interest in qlty CLI adoption.
When should I use this skill?
The user requests lint checks, formatting fixes, code metrics, or pre-commit quality validation across multiple languages.
What you get
Lint reports, auto-fixed formatting, and complexity or duplication metrics from qlty CLI runs.
- lint report
- formatted source files
- complexity metrics
By the numbers
- Supports 70+ linters via qlty CLI
- Covers 40+ programming languages
Files
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 --smellsParameters
| 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 --fixQuality 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 --smellsInitialize in New Repo
uv run python -m runtime.harness scripts/qlty_check.py --init --cwd /path/to/repoDirect CLI (if qlty installed)
# Check changed files
qlty check
# Auto-fix
qlty check --fix
# JSON output
qlty check --json
# Format
qlty fmtRequirements
- qlty CLI: https://github.com/qltysh/qlty
- MCP server:
servers/qlty/server.pywraps CLI - Config:
.qlty/qlty.tomlin repo (runqlty initfirst)
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 |
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kHow it compares
Pick qlty-check over single-language linter skills when a polyglot codebase needs one CLI for lint, format, and metrics before handoff.
FAQ
How many linters does qlty-check support?
qlty-check uses the qlty CLI which supports 70+ linters across 40+ programming languages, providing a single entry point for linting, formatting, and metrics.
What qlty-check commands are available?
qlty-check exposes harness commands for checking changed files with --fix, scanning all files with --all, and format-only passes with --fmt via scripts/qlty_check.py.