Use a skill for your first code review

Install one review skill, give it a diff scope and bans. Do not let it push a branch.

In the skills directory, find a review or PR playbook. Confirm the description is a checklist, not some other domain.

After install, name the skill in chat and state: current diff only, no unrelated files, stop if you see a secret.

A skill has no hands. To read the repo, add one filesystem or version-control MCP narrowed to that tree.

See MCP vs skills and how to pick a skill. You merge the comments. Do not auto-push.