split-mr
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.
SKILL.md
The description above is the indexed summary. With JavaScript enabled, this page also loads the SKILL.md text from GitHub.