crew-address-findingslisted

# Address Code Review You are working through the findings from a crew-afk code review report. Follow every step below in order. ## Tracker Configuration Before any tracker operation, locate `issue-tracker.md` using this lookup chain: 1. `$(git rev-parse --show-toplevel)/.coding-crew/docs/issue-tracker.md` (project-level) If it does not exist, invoke the `configure-tracker` skill now to set it up, then continue. All tracker operations in this skill use the operation definitions in that file. **Examples:** ```bash /crew-address-findings # uses latest report /crew-address-findings path/to/report.md # uses custom report ``` ## Step 0 — Branch safety check **Check current branch:** This skill works on existing PR branches. Do not run on the default branch. ```bash bash "<skill-dir>/scripts/branch-safety-check.sh" ``` If on the default branch, the script exits with an error. If on a non-default branch, continue to Step 0.1. ## Step 0.1 — 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** — scan for pending reviews across all feature directories: ```bash # Find all review files under .scratch/*/reviews/