Agent skill · Code Review & Quality

qlty-check

Code quality checks, formatting, and metrics via qlty CLI

parcadeigithub.com/parcadeiGitHub ↗
claude-codecan modify filesMIT
Install
npx skills add parcadei/Continuous-Claude-v3 --skill qlty-check --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 2 KB
Bundled scripts: none
Allowed tools: BashRead
Path: .claude/skills/qlty-check/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 3,879
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 | | `--p

What's inside
Steps it walks through
  1. When to Use
  2. Quick Reference
  3. Parameters
  4. Common Workflows
  5. After Implementation
  6. Quality Report
  7. Initialize in New Repo
  8. Direct CLI (if qlty installed)
  9. Requirements
  10. vs Other Tools
Commands it runs
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
More from Continuous-Claude-v3
All skills →
slash-commandsCreate and use Claude Code slash commands - quick prompts, bash execution, file referencesAI & Agentssub-agentsCreate and configure Claude Code sub-agents with custom prompts, tools, and modelsAI & Agentstdd-migrateTDD workflow for migrations - orchestrate agents, zero main context growthWorkflow & Productivitytdd-migration-pipelineOrchestrator-only workflow for migrating/rewriting codebases with full TDD and agent delegationDatabasescompound-learningsTransform session learnings into permanent capabilities (skills, rules, agents). Use when asked to…Otherskill-upgraderUpgrade any skill to v5 Hybrid format using decision theory + modal logicAI & Agents
About this skill
What does the qlty-check skill do?

Code quality checks, formatting, and metrics via qlty CLI

How do I install it?

Run `npx skills add parcadei/Continuous-Claude-v3 --skill qlty-check --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From parcadei/Continuous-Claude-v3, a repository with 3,879 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.