Candid Chrome QA Fix

Consume a candid-chrome-qa findings file (v2.0 schema) and turn it into actual code fixes — with optional issue-tracker filing.

This is a technique skill. Follow the order. Sit alongside /candid-chrome-qa (the producer) and /candid-loop (the analogue for candid-review issues).

Workflow

Execute these steps in order.

Step 1: Resolve the findings file

Precedence (highest to lowest):

1. CLI flag --file <path> — use that exact file. If it doesn't exist or isn't readable, abort.
2. Latest file by mtime in .context/findings/*.json.
3. If .context/findings/ is empty/missing, output the message below and stop: