smelllisted

# Smell Review Run a targeted structural smell analysis on a specific target or the current working-tree changes. ## 1. Determine the target - If the user supplied **file paths**, use those directly. - If the user supplied a **directory**, analyze all source files within it (skip `bin/`, `obj/`, `node_modules/`, `dist/`, `migrations/`). - If the user supplied a **PR number**, run `gh pr diff <number> --name-only` to get the changed files, then use those. - If **no target was supplied**, run `git diff main...HEAD --name-only` (or `git diff HEAD --name-only` if on main) to discover changed files. Confirm the list with the user before proceeding. Filter the file list to source code only: - **Include:** `.cs`, `.ts`, `.vue`, `.tsx`, `.jsx`, `.py`, `.go`, `.java`, `.rb`, `.rs` - **Exclude:** config files (`.json`, `.yaml`, `.toml`, `.xml`), migrations, SQL scripts, test fixtures, generated files If the filtered list is empty, tell the user: "No source code files found in the target — smell-reviewer analyzes application logic, not config or documentation." ## 2. Run smell-reviewer Dispatch the `smell-reviewer` agent with: - The filtered list of file paths - Any relevant context the user provided (e.g., "focus on the service layer", "we just refactored this module") - The contents of `docs/CONVENTIONS.md` if it exists (so the agent can read suppressions without a separate file read) ## 3. Present findings The smell-reviewer agent will produce a severity-labele