ensemble-reviewlisted

## Context marker 🧠🧠🧠 When the skill activates, begin the first commentary update with `🧠🧠🧠` and a concise `Using ensemble-review ...` announcement. Do not repeat the marker on later updates unless another skill activates. # Ensemble Review Review one file with three independent validators, then synthesize their findings. Blind agreement is strong evidence; well-supported disagreement is useful evidence. The synthesis is the deliverable. Raw reports are transient evidence. ## Input and scope - Require one readable file. Resolve a relative path from the working directory. If it is missing or ambiguous, ask; do not guess. Do not accept a directory. - Never send credential material to a reviewer. Reject files whose name or path indicates secrets or credentials, including `.env*`, `secrets/`, `*.pem`, `*.key`, `*.crt`, and private-key or token exports. Do not inspect those files to decide whether they are safe. - Accept optional extra instructions. Without them, use a file-type-appropriate focus: prose and plans → structure, consistency, and gaps; source code → correctness, clarity, and edge cases. - Do not edit the target unless the user separately requests edits. ## External-review consent `pi` sends the complete attached file and the review prompt to the selected third-party model providers. Before the first `pi` invocation, tell the user which providers will receive it and obtain explicit consent in the current conversation. Treat a request for an en