address-code-reviewlisted

# Address Code Review You are working through the findings from an afk-sprint code review report. Follow every step below in order. ## Step 0 — Install dependencies Follow the `dep-install` skill to ensure dependencies are installed. ## Step 1 — Locate the report Determine the report source in this order: 1. **Inline content** — if the user pasted review findings directly into the conversation, use that content. Skip the remaining options. 2. **File path argument** — if the user passed a file path, read it. 3. **Auto-detect** — find the latest report: ``` ls -t .scratch/reviews/*.md | head -1 ``` If no report is found via any of the above, tell the user and stop. If using a file, print the path so the user knows which file is being processed. ## Step 2 — Parse all findings Read the report file. Extract every finding — each `[CRITICAL]`, `[HIGH]`, `[MEDIUM]`, and `[LOW]` block across all branches. Group findings by branch so related items are reviewed together. ## Step 3 — Challenge each finding For every finding, do the following **before** deciding whether to act on it: 1. Read the referenced file at the exact line(s) cited. 2. Ask yourself: - Is the reviewer correct about the problem they've identified? - Is their proposed fix the best approach, or is there a simpler / more idiomatic alternative? - Does the change fit the project's conventions and domain language? - Could addressing it introduce new bugs or regressions? - Has this alrea