Skip to content

parcadei/Continuous-Claude-v3 / .claude/skills/qlty-check

qlty-check

Verified

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

# 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

ParameterDescription
--checkRun linters (default)
--fixAuto-fix issues
--allProcess all files, not just changed
--fmtFormat files instead
--metricsCalculate code metrics
--smellsFind code smells
--pathsSpecific files/directories
--levelMin issue level: note/low/medium/high
--cwdWorking directory
--initInitialize qlty in a repo
--pluginsList 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

vs Other Tools

ToolUse Case
qltyUnified linting, formatting, metrics for any language
ast-grepStructural code patterns and refactoring
morphFast text search
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 321kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 321kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 321kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 321kUpdated Claude CodeCodexVerifiedInstall