pattern-reviewer-coding-standardlisted

# pattern-reviewer-coding-standard ## When to activate - The dispatched caller is reviewing a `type:backend` / `type:frontend` task's production-code diff. - A user says "review this diff for quality", "look for bugs", "audit the change". - Do NOT activate for `type:e2e`. ## Project memory overlay After loading this skill, also check `$MAIN_ROOT/.claude/memory/patterns/pattern-reviewer-coding-standard.md` in the consuming project (resolve `MAIN_ROOT="$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")"`). If present, load it as an **additive overlay** to the rules below; if absent, skip silently. See `memory-convention` for the full contract (additivity, severity floor, conflict surfacing). ## References | Reference | When to read | |-----------|--------------| | `templates/review-comment.md` | Always read before composing the comment body. The finding rows must match this shape verbatim so downstream fix passes can parse them. | ## Iron rules for every finding - **>80% confidence filter.** Report only when you are >80% confident. Skip stylistic preferences unless they violate a documented convention. Skip issues in unchanged code unless they are CRITICAL security. Consolidate similar findings. - **Cite `path/to/file.ext:line`.** Quote the offending snippet in a BAD block; show the fix in a GOOD block (or a one-sentence fix when a snippet is overkill). - **Read surrounding code.** Open the full file; follow imports; check call sites. If you cannot un