qualitylisted

# DLC: Code Quality Check Run code quality analysis against the current project and create a GitHub issue with findings. Before running, **read [../dlc/references/ISSUE-TEMPLATE.md](../dlc/references/ISSUE-TEMPLATE.md) now** for the issue format, and **read [../dlc/references/REPORT-FORMAT.md](../dlc/references/REPORT-FORMAT.md) now** for the findings data structure. ## Step 1: Detect Linting Config Scan for linting configuration and project type: | Config File | Linter | Language | |-------------|--------|----------| | `.eslintrc*` / `eslint.config.*` / `biome.json` | ESLint / Biome | JS/TS | | `ruff.toml` / `pyproject.toml` (with `[tool.ruff]`) | Ruff | Python | | `.golangci.yml` / `.golangci.yaml` | golangci-lint | Go | | `clippy.toml` / `Cargo.toml` | Clippy | Rust | | `.rubocop.yml` | RuboCop | Ruby | Also check for formatter configs: `.prettierrc*`, `.editorconfig`, `rustfmt.toml`. ## Step 2: Run Quality Tools ### Linting Run the detected linter with JSON/machine-readable output: Select the tool based on availability (`command -v`), not exit codes — linters exit non-zero when issues are found, which is a valid result to capture. ```bash # JS/TS — select by availability if command -v eslint >/dev/null 2>&1; then eslint . --format=json 2>/dev/null elif command -v biome >/dev/null 2>&1; then biome check . --reporter=json 2>/dev/null fi # Python — prefer Ruff, fall back to flake8 if command -v ruff >/dev/null 2>&1; then ruff check . --output-format=json 2>