What problem does it solve? Flipping production traffic from a legacy app to a migrated page is risky and irreversible if done before verification gates pass. This Skill enforces a gated, two-PR feature-flag workflow so a route flip only happens after verify, e2e, and parity gates all pass, with a safe revert path. ## Core Features & Use Cases - Four flip actions: --flag-off prepares the routing artifact and flag (default OFF) for the code PR, --flag-on activates the path flip, --flag-on --confirm-live records human confirmation that the merged flip is live, and --revert rolls back an in-flight or live flip. - Dual edge mechanisms: edits the nginx config or the CloudFront behavior manifest depending on the app's configured flipMechanism, with identical flip semantics. - Gate-evidence freshness checks: recomputes content hashes of the page's source paths, shared package dependencies, and migration plan before allowing a flip, blocking on stale or uncommitted evidence. - Use Case: After a migrated hotel booking page passes all gates, run --flag-off to prepare the nginx route in PR1, then --flag-on to cut over the path in PR2 once the code PR merges. ## Quick Start Run fm-route with the page name and --flag-off to prepare the routing artifact for the code PR once all migration gates have passed.
