review-branch — moved into gitlab-review
⚠️ Deprecated as a standalone skill. The whole-branch review workflow that used to live here now lives in one canonical place: the
gitlab-reviewskill, under thereview the whole branchtrigger. Same move thecommitskill made intogitlab-flow.
Keeping two copies caused real drift: this file went without a severity model entirely while gitlab-flow had carried one since commit 733261d, and a single fix later had to be applied twice, in two languages. One canonical home is the fix.
Use this instead
npx skills add nguyenvanchiens/skills_end_to_end -s gitlab-flow -y -a claude-code --copy
npx skills add nguyenvanchiens/skills_end_to_end -s gitlab-review -y -a claude-code --copy
gitlab-review depends on gitlab-flow — install both. Rather than copying them, it reads six things from gitlab-flow: the severity model, the review-lens catalogue, the base-branch rules, the output-language rules, the safety rules, and Steps 1-3 of review the last change (the grounding rubric its agent prompts are keyed to).
Then type review the whole branch. The workflow is unchanged: four specialized agents in parallel → dedup + verify → auto-fix the Blocker/Major findings that survive verification.
Not using GitLab / glab?
review the whole branch only needs git. glab shows up in two optional spots — resolving the base branch from an open MR, and pulling the task description from an MR — and you can skip both. The other three gitlab-review triggers (review the MR !N, post review result to the MR, merge the request) do need glab — don't type them if you don't use GitLab.
If you want it gone entirely
This file is a deliberate pointer, not the spec. To remove the standalone skill completely, delete the skills/review-branch/ directory and drop its row from the README — nothing depends on it.