team-review

The skill's footprint is coherent with its stated purpose of orchestrating a three-role code review and fix pipeline. It relies on controlled role specification files, internal task and messaging systems, and per-session artifacts. While the design presents broad tool permissions, there is no evident pattern of unverifiable binaries, credential harvesting, or external data exfiltration in the current description. Maintain strict role-data boundaries, enforce access controls on wisdom/artifact directories, and ensure role-specs come from trusted sources to preserve security posture.