Best use case
qlty-check is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Code quality checks, formatting, and metrics via qlty CLI
Teams using qlty-check should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/qlty-check/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How qlty-check Compares
| Feature / Agent | qlty-check | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Code quality checks, formatting, and metrics via qlty CLI
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 |
Related Skills
saas-launch-checklist
Pre-launch verification across infrastructure, security, legal, payment, email, analytics, and performance. Day-1 monitoring, rollback plan, incident response skeleton, and post-launch week-1 checklist.
qlty-during-development
QLTY During Development
fp-check
Systematic false positive verification for security findings. Provides structured methodology to confirm or dismiss scanner results, manual audit findings, and automated alerts. Adapted from Trail of Bits. Use when triaging security scan results or verifying audit findings.
factcheck-guard
Use this skill when making any factual claim about the codebase — existence, absence, or behavior. Converts the claim-verification rule into a systematic action protocol that prevents false assertions from grep-only results.
completion-check
Completion Check: Verify Infrastructure Is Wired
workflow-router
Goal-based workflow orchestration - routes tasks to specialist agents based on user goals
wiring
Wiring Verification
websocket-patterns
Connection management, room patterns, reconnection strategies, message buffering, and binary protocol design.
visual-verdict
Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS/REVISE/FAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.
verification-loop
Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.
vector-db-patterns
Embedding strategies, ANN algorithms, hybrid search, RAG chunking strategies, and reranking for semantic search and retrieval.
variant-analysis
Find similar vulnerabilities across a codebase after discovering one instance. Uses pattern matching, AST search, Semgrep/CodeQL queries, and manual tracing to propagate findings. Adapted from Trail of Bits. Use after finding a bug to check if the same pattern exists elsewhere.