qualitylisted

# Quality: Code Review, Cleanup, and Formatting Review all changed files for quality issues. Fix any issues found. ## Phase 1: Identify Changes Run `git diff` (or `git diff HEAD` if there are staged changes) to see what changed. If there are no git changes, review the most recently modified files that the user mentioned or that you edited earlier in this conversation. Then create a clean results directory for the review agents: ```bash rm -rf quality-results && mkdir quality-results ``` ## Phase 2: Launch Review Agents in Parallel Use the Agent tool to launch all agents concurrently in a single message. For each Agent call, set `model: "claude-sonnet-4-6"` and `effort: "medium"`. Pass each agent the full diff so it has the complete context. **CRITICAL SCOPE RULE:** All review agents must ONLY flag issues in code that was added or modified compared to what we branched out from. Never flag, remove, or suggest changes to pre-existing code that was not touched by the current changes. If pre-existing code has issues, it is out of scope. **RESULTS OUTPUT:** Each agent MUST write its findings to a file in the `quality-results/` directory. Use the Write tool to create the file. If no issues are found, write "No issues found." to the file. The file is the source of truth — the agent's return message is just a brief summary. **File format for each agent's results file:** ```markdown # [Category] Findings ## Issue 1: [Short description] **File:** path/to/file **Line:** 42 **Seve