verify-quality

# Code Quality Verification ## Purpose Verify code for quality anti-patterns including poor naming, missing documentation, magic values, and organizational issues. All analysis happens locally. ## When to Use Trigger this skill when the user asks to: - "verify agent quality" - "verify quality" - "check code quality" - "review code organization" - "check naming conventions" > **Note:** For full verification including security, patterns, and language-specific checks, tell the user to say **"verify agent"**. ## Process ### Step 1: Discover Files Locate files to analyze: **Source files:** - `*.py`, `*.ts`, `*.js`, `*.go`, `*.rs` - Source code - Focus on main implementation files, not tests **Directories to check:** - `src/`, `lib/`, `app/`, project root - `agent/`, `tools/`, `utils/` **Exclude:** - `node_modules/`, `.venv/`, `venv/`, `__pycache__/` - Test files (`*.test.*`, `*.spec.*`, `*_test.go`) - Generated files, migrations ### Step 2: Run Quality Checks All checks in this skill are **`[HEURISTIC]`** — they require judgment. Tag findings with `[H]`. --- #### 2.1 `[HEURISTIC]` Naming Conventions **Check for:** | Issue | Examples | |-------|----------| | Single-letter variables (except loops) | `x = get_data()`, `d = {}` | | Unclear abbreviations | `proc_usr_req()`, `calc_val()` | | Inconsistent casing | Mixing `camelCase` and `snake_case` in same file | | Names that don't describe purpose | `data`, `temp`, `result`, `info` | | Boolean names without is/has/can ...