What problem does it solve? Upgrading a Lens module without checking schema and version compatibility can break repository topology or leave legacy layouts in an inconsistent state. This Skill inspects the current module configuration, decides whether an in-place upgrade is safe, and routes legacy layouts to the proper migration path instead of guessing. ## Core Features & Use Cases - Compatibility Detection: Loads module config from the control repository and detects the current schema, version, and topology state. - Upgrade Decision Routing: Produces a deterministic decision of no-op, in-place upgrade, or handoff to the legacy migration route. - Structured Action Plans: Emits an upgrade or migration action plan plus a compatibility report, with a dry_run mode that plans without mutating state. - Use Case: A maintainer points the Skill at their control and governance repositories, runs it in dry-run mode, and receives a report showing the detected schema, the chosen upgrade route, blocking issues, and the suggested next command. ## Quick Start Ask the assistant to check whether the Lens module in your control repository can be upgraded in place or needs a legacy migration, using dry-run mode first.
