split-branch-for-review

To check if your git branch is too large for code review, analyze the size of code changes relative to a target branch using line count and complexity metrics. This Skill evaluates branch size against maintainability requirements to recommend splitting for better PR readiness.

You should split a git branch before creating a pull request when branch size analysis indicates the line count and code complexity exceed maintainability requirements. Splitting improves code review quality and collaboration by making changes easier to inspect.

Yes, you need git-lfs installed to analyze branch size for PR readiness. The analysis requires git, git-lfs, and the diff-line-budget.sh script to operate correctly, gathering commit data and calculating line counts to assess splitting necessity.

The best way to evaluate PR readiness for a feature branch is to run a branch size analysis against a target branch like main. This uses Git to gather commit data and provides recommendations on whether to split based on line count and code complexity.

To run a branch splitting recommendation against the main branch, execute the command '/split-branch-for-review main'. This triggers the analysis script to measure code changes and advise whether splitting improves review quality and maintainability.