review-fix-workerlisted

# Review Fix Worker Read one review file under `reviews/`, fix every `open` finding one by one, and mark each finding's status in the file immediately after it is resolved. The review file is the complete contract: it carries the repository root, branch, base, task path, change class, and validation tier, so this skill works from a fresh context with no other input. Invocation authorizes modifications to the branch named in the review file for non-security remediation. Never expand scope beyond the frozen finding set. Never delete, stage, or commit review files; they are ignored workflow state retained across review passes. `finish-task` removes all review files associated with the completed task after its PR is CI-green. ## Efficient evidence handling Keep the main context for decisions, behavioral TDD evidence, and targeted source inspection. Delegate broad, read-only interpretation to isolated subagents when available and require concise structured results. Do not delegate primary RED-GREEN decisions, concurrent edits, or stateful checks that share a database, port, simulator, fixture, generated output, or external service. Use the smallest evidence that proves a result. Broad commands and full test output belong in the task log directory; return the exit status, duration, concise result, relevant failure excerpt, and log path. Use stable names such as `unit.log` or `typecheck.log` and overwrite a superseded passing log instead of accumulating timestamped copies. Enfo