electron-review

name	electron-review
description	Use when an independent context must assess an Electron task, diff, security boundary, tests, or release evidence before acceptance. Do not use for initial implementation, speculative rewrites, or fixes before findings are evidenced.

Electron Review

Start read-only. Review the requirement and evidence, not the author's confidence.

1. Read the sidecar contract, matching track/task, references/code-review-standard.md, and references/review-checklist.md.
2. Establish the exact task scope and base/head diff or file set; preserve unrelated changes.
3. Independently run risk-proportionate checks and compare behavior with PRD/architecture/plan.
4. Prioritize security/data loss, crashes/main flows, races/cleanup/platform/package differences, then maintainability.
5. Record each actionable finding with severity, file/line, trigger, consequence, evidence, minimal fix, and regression test.
6. Reproduce P0-P2 findings when feasible before requesting or applying a fix.
7. Write findings and verdict in the task Review section; a review from the same context is explicitly SELF_REVIEW_REDUCED_INDEPENDENCE. Host brand neither grants nor removes independence. List every NOT RUN check.

Do not report style preference as a defect, trust claimed tests, or rewrite code before the findings pass is complete.