What problem does it solve? Migrating a Xojo desktop project from API 1.0 to API 2.0 is not a simple rename: functions like InStr change their not-found sentinel, Mid changes index base, and Date shifts its epoch by 66 years, so a rename that compiles can still be wrong. This Skill provides a rule-driven, confidence-tiered migration workflow that fixes semantics before names and commits one category at a time. ## Core Features & Use Cases - Deprecation matrix and conversion rules: Covers more than a thousand deprecated and removed symbols with hundreds of vetted find/replace rules, caveats, and worked examples. - IDE-driven and scanner-based inventory: Joins Xojo IDE Analyze Project output to the rules via worklist.py, with scan.py as a fallback and cross-platform closing check. - Checkpointed, reversible workflow: Each category ends with an IDE analyze checkpoint, a diff against the previous checkpoint, and a single git commit, so any over-matching rule can be reverted alone. - Use Case: Ask the agent to migrate your text-format Xojo project on a clean git branch; it inventories deprecated symbols, applies high-confidence rules, hand-converts Date and error-handling code, and reports falling warning counts at every checkpoint. ## Quick Start Run /xojo:xojo-migrate in Claude Code (or write $xojo-migrate in Codex) with your Xojo project on a clean git branch to start the guided API 2.0 migration.
