What problem does it solve? Code changes often ship with unclear contracts, tangled diffs, and accumulating technical debt because developers skip clarification, mix refactoring with features, or ignore linter warnings. This Skill provides a disciplined workflow for anyone writing code so every change is understandable, testable, and reviewable. ## Core Features & Use Cases - Clarify before coding: Define inputs, outputs, invariants, and error cases, then locate the existing contract and pick the smallest change point with a failing-then-passing test. - Safe refactoring: Characterize current behavior with tests, apply one small transformation at a time, and keep broad refactoring in a separate change from the feature. - Debt triage: Run the project's formatter, linter, and tests declared in AGENTS.md, distinguish mechanical warnings from real risks, and convert larger debt into trackable items. - Use Case: While executing a kanban task in a PoP-managed repository, apply this Skill to write a behavior description, produce a test that fails before and passes after the change, and deliver a diff with a single intention. ## Quick Start Apply the clean-code-change skill to plan and implement my next code change with a clear contract, a protecting test, and a single-intention diff.
