Review MR

Review another developer's merge request and write a verdict, the findings, and the acceptance-criteria check to a local markdown file.

This is not /review-axes. That one reviews your code against the repo's standards and the originating spec. This one reviews someone else's code along four axes (Correctness, Security, Performance, Design) where nobody has told you what the code was supposed to do beyond what the MR itself claims.

Two reviewers only, deliberately: this session covers Correctness + Security, and a single sub-agent covers Performance + Design. Keeping it to two is a cost decision, respect it.

The task passed in at invocation is a starting point, not the whole picture. The skill asks the user what the diff can't answer (step 3) before it judges anything, then opens the report with a verdict so the reader knows in one line whether this merges.

Everything this skill writes is in English, whatever language the MR or the surrounding conversation is in.

Process

1. Resolve the input

Three modes. Detect which by looking at git remote get-url origin: