Code quality checks, formatting, and metrics via qlty CLI
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 |
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
BluOS CLI (blu) for discovery, playback, grouping, and volume.
Search and analyze your own session logs (older/parent conversations) using jq.
Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Claude Code: use --print --permission-mode bypassPermissions (no PTY). Codex/Pi/OpenCode: pty:true required.
OpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.
Query Google Places API (New) via the goplaces CLI for text search, place details, resolve, and reviews. Use for human-friendly place lookup or JSON output for scripts.
Category:developer