Phy Pr Size Splitterv1.0.3

A backend platform team mandates that no PR over 400 changed lines gets merged before a size assessment. Engineers run the skill against their branch, receive a classification and a chunk-level split plan (schema migration first, then business logic, then tests), and either split the PR or attach the justification comment. Review throughput improves measurably because reviewers stop opening 1,200-line 'unmergeable' diffs.

Maintainers of a popular open-source repository receive large community contributions and need a fast, consistent way to respond. The skill measures the incoming PR, classifies it, and generates a ready-to-post comment with a concrete split checklist and suggested branch names. Triage becomes fair and repeatable instead of maintainer-mood-dependent.

A team performing a framework upgrade or database migration uses the skill to separate mechanical refactors, config changes, and schema migrations from behavioral changes. Because the tool identifies dependency order between chunks, the split sequence is obvious and each PR can be rolled back independently if a regression appears in production.

A tech lead uses the skill deliberately on their own work during code review pairing sessions to teach juniors what 'atomic' means in practice. The classification output (review time, bug-catch rate estimates) makes the cost of oversized PRs concrete and motivates better habits before juniors acquire bad ones.

A CI team wraps the classification logic into a GitHub Action that comments on every PR and optionally blocks merges above a threshold unless an override label is applied. The split-plan output becomes a suggested remediation path in the failure message, reducing friction and argument.

The skill itself stays Apache-2.0 and self-hosted via the gh CLI, building trust and adoption. Revenue comes from a hosted dashboard that aggregates PR size trends across repos, tracks team review-quality metrics over time, and enforces org-wide policies with historical reporting.

Sold as a module inside an existing developer-productivity or code-governance platform (e.g., bundled with code-review, static-analysis, or engineering-metrics suites). Enterprises buy it because it plugs into their existing GitHub Enterprise or GitLab instance with SSO, audit logs, and policy configuration.

The skill is a free lead magnet; the business sells workshops, code-review-culture consulting, and custom CI integrations that help teams adopt PR size discipline. The value is in change management, not the tool itself.