What problem does it solve? Type checking alone misses manual mappings, serialized fields, and assertions hidden behind casts, so cross-layer changes like renames or contract updates often leave stale references behind. This Skill systematically sweeps every layer that consumes a changed value before you report the work as complete. ## Core Features & Use Cases - Change Axis Classification: Records whether the change is a type narrowing, field rename, configuration default, contract evolution, or display wording update, with a gap checklist per axis. - Paired Old/New Search: Searches both old and new expressions across source, comments, tests, fixtures, snapshots, and documentation to reveal layers that adopted only part of a change. - End-to-End Verification: Requires an assertion at the final observable layer, such as rendered text, serialized output, or a database-backed read, plus affected tests and type checks. - Use Case: After renaming a configuration field that flows from storage through a local service to the TUI, use this Skill to find stale schema entries, outdated fixtures, and old labels in docs, then verify the rendered output reflects the new name. ## Quick Start After completing a rename or contract change, ask the agent to run a cross-layer drift sweep over the affected data flow and report any stale references.
