Menú
Code quality checks, formatting, and metrics via qlty CLI
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
Connect to the running Redmine instance and log in via the Playwright MCP browser, using REDMINE_PLAYRIGHT_URL/REDMINE_PLAYRIGHT_USER/REDMINE_PLAYRIGHT_PASSWORD environment variables. Use whenever the user asks to open, check, access, or test something in the running Redmine UI (e.g. verifying a feature in the browser, taking a screenshot of a page, manually exercising a flow).
Stage the current changes and create a git commit with a properly formatted English message. Use whenever the user asks to commit, save, or check in their work. Picks a Conventional-Commits-style prefix (fix:, feat:, refactor:, docs:, test:, chore:, style:, perf:) based on the actual diff, keeps the first line a concise summary, and adds a bullet list of details only when the change touches several things.
Execute the implementation plan by processing and executing all tasks defined in tasks.md
Execute the implementation planning workflow using the plan template to generate design artifacts.
Create or update the feature specification from a natural language feature description.
Basado en la clasificación ocupacional SOC
| name | qlty-check |
| description | Code quality checks, formatting, and metrics via qlty CLI |
| source | https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/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 |