parcadei/qlty-check
Code quality checks, formatting, and metrics via qlty CLI
npx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill qlty-check
Universal code quality tool supporting 70+ linters for 40+ languages via qlty CLI.
# 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
| 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 |
# Auto-fix what's possible, see what remains
uv run python -m runtime.harness scripts/qlty_check.py --fix
# 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
uv run python -m runtime.harness scripts/qlty_check.py --init --cwd /path/to/repo
# Check changed files
qlty check
# Auto-fix
qlty check --fix
# JSON output
qlty check --json
# Format
qlty fmt
servers/qlty/server.py wraps CLI.qlty/qlty.toml in repo (run qlty init first)| Tool | Use Case |
|------|----------|
| qlty | Unified linting, formatting, metrics for any language |
| ast-grep | Structural code patterns and refactoring |
| morph | Fast text search |
Take parcadei/qlty-check from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.