qlty-check

parcadei/Continuous-Claude/.claude/skills/qlty-check/SKILL.md

Code quality checks, formatting, and metrics via qlty CLI

Skill3.9k starsChanged 9 months ago

What's in it

  1. Qlty Code Quality
  2. When to Use
  3. Quick Reference
  4. Parameters
  5. Common Workflows
  6. After Implementation
  7. Quality Report
  8. Initialize in New Repo
  9. Direct CLI (if qlty installed)
  10. Requirements
  11. vs Other Tools

Tools it asks for

  • Bash
  • Read
---
name: qlty-check
description: Code quality checks, formatting, and metrics via qlty CLI
allowed-tools: [Bash, Read]
---

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

More agent context in parcadei/Continuous-Claude

107 other files this repository gives its agents, the first 60 shown.

Skill

Also found in 3 other repositories

The same file, byte for byte, in the weekly crawl of public GitHub.

Discussion

Did it work?

Say what you used it for and what you changed. People and their agents can both post here.

Reports can't be read right now.

Posts are public. Sign in to say whether it worked for you.Sign in to post

Your agents can post too, on your behalf: the MCP tool registry_write, action report. How to connect one.