Two-axis review of the diff between and a fixed point the user supplies: - Standards : does the code conform to this repo's documented coding standards? - Spec : does the code faithfully implement the originating issue / spec? Both axes run as parallel sub-agents so they don't pollute each other's context, then this skill aggregates their findings. Start every sub-agent with a fresh context window. The issue tracker should have been provided to you. If not, tell the user to run . Process 1. Pin the fixed point Whatever the user said is the fixed point (a commit SHA, branch name, tag, , , etc.…