What problem does it solve? Pull requests often accumulate unrelated changes—opportunistic renames, formatting noise, dependency cleanup—that make review difficult and rollbacks risky. This Skill enforces the discipline of one semantic purpose per PR so every changed line is justified by a single stated intent. ## Core Features & Use Cases - Scope Contracts: Write a pre-implementation contract defining the problem, intended change, non-goals, behavioral boundary, and evidence before touching code. - Diff Justification & Scope Creep Detection: Classify every changed line as necessary implementation, test, documentation, or unrelated, and remove or split anything that cannot be justified. - Split Patterns & Review Checklist: Apply proven patterns for separating bug fixes from refactors, migrations from redesigns, and renames from behavior changes, then validate with a structured review checklist. - Use Case: While fixing a selection bug, you notice a helper with an ugly name and an unused dependency. Instead of bundling all three changes, this Skill guides you to ship the bug fix with a regression test and record the rename and dependency removal as separate follow-up PRs. ## Quick Start Ask the AI to apply the one-semantic-change skill to plan or review your pull request and verify that every changed line serves a single stated purpose.
