gitlabhq

GitLab workflow automation using glab CLI

MUST USE before planning, implementing, refactoring, OR reviewing any GitLab code changes (including merge request reviews, code review feedback, new features, bug fixes). Evaluate every principle group to ensure cross-domain coverage. Triggers: review, reviewing, plan, planning, implement, implementing, refactor, refactoring, MR review, code review.

Analyze the changes on the current branch — both uncommitted work and commits already made (e.g. a PoC or existing MR) — and reason about whether they should be split into smaller, more focused MRs. Identifies natural boundaries (backend/frontend, model/spec, feature/refactor) and proposes a split plan or confirms the changes are cohesive enough to keep as one.