What problem does it solve? Codebases accumulate duplicated definitions — the same literal, shape, or rule defined in multiple places across language, database, and wire boundaries — causing drift, sync bugs, and change amplification. This Skill systematically hunts those single-source-of-truth violations and turns them into an adjudicated, actionable findings report instead of raw grep noise. ## Core Features & Use Cases - Ten Symptom Classes: Detects multi-source literals, shape proliferation, word overload, legacy-vocabulary mapping layers, dual-pathway behavior forks, scattered defaults, pure-subset shape pairs, same-name-different-shape types, redundant conversion chains, and re-implemented derivations. - Honest Adjudication: Distinguishes real violations from idiomatic false positives (module-qualified names, forward contracts, trust-boundary re-validation, frozen wire literals) with a mandatory not-counted list. - Treatment Recipes: Routes every confirmed finding to a concrete disposition — codegen, parity guard, constant promotion, typed payload, convert-at-the-edge, single rule owner, vocabulary close-out, adjudication, or pin-test deletion. - Use Case: When a user asks "do these two definitions stay in sync?" or "why is this constant defined twice?", sweep the repo's cross-stack seams and deliver a numbered report (S1, S2...) with file:line evidence, severity, and per-finding disposition. ## Quick Start Ask the agent to check whether the event type constants in this repo are defined in more than one place and produce an SSOT findings report.
