What problem does it solve? Before migrating a legacy OhMyHotel Angular page, component, service, or store, teams need a structured understanding of its dependencies, cross-app differences, and risk profile. This Skill automates that analysis and produces a machine-readable baseline that every later migration step depends on. ## Core Features & Use Cases - Automated legacy analysis: Launches an isolated analyzer agent that writes analysis.json containing the dependency graph, shared-package candidates, 3-app diff (pc/mobile/hana), and required gates. - State and safety guards: Refuses to run on flipped, done, or flip-in-flight pages, warns before demoting verified pages, and enforces per-page and tracker locks to prevent concurrent corruption. - Advisory audit: Optionally spawns an independent Codex audit of the analysis stage without changing page status. - Use Case: A developer starting the migration of the hotel-booking-info page runs this Skill to get its risk level, required gates (webview, telemetry), and shared-package extraction candidates before planning. ## Quick Start Ask the assistant to analyze the legacy page hotel-booking-info for the pc app using the fm-analyze skill.
