multi-lens-review
Multi-Lens Review
Use this skill to walk a single change or decision through several review lenses and synthesize the findings into one decision with required actions and residual risk.
This skill describes lenses a single assistant adopts in turn. It is not a multi-agent panel. The lenses are perspectives, not independent reviewers — apply each honestly and resist consensus when a lens surfaces a genuine concern.
When to Use
Use this skill when a change is non-trivial enough that one lens alone would miss material risk:
- A spec, design, implementation, or workflow that affects more than one concern (correctness, security, data, UX, ops).
- A change where required fixes and follow-ups must be separated for a merge decision.
- A review that has to reconcile tradeoffs between lenses (e.g. ergonomics vs. security, speed vs. correctness).
Do not use it for single-lens questions that have an obvious owner (e.g. "is this regex correct?", "does this CSS validate?"). When the work is squarely a single concern — one focused security check, one framework-specific review, one gate decision — handle it as a focused single-concern task; reach for multi-lens-review when the work spans several concerns.