What problem does it solve? Upgrading the Google Play Billing Library across major versions involves breaking API changes, removed methods, and new SDK requirements that are easy to miss. This Skill automates the detection, planning, and execution of a safe migration path so your in-app purchase code keeps working on the latest PBL release. ## Core Features & Use Cases - Effective Version Detection: Scans build files and source code for deprecated APIs (like SkuDetails) to determine the true baseline version, even when the declared dependency version is misleading. - Direct or Stepped Migration Planning: Calculates whether to jump directly to the target version or migrate two major versions at a time, with intermediate build verification at each step. - Intent-Based Refactoring: Replaces legacy patterns with modern equivalents, such as swapping SkuDetails for ProductDetails, ProrationMode for ReplacementMode, and manual reconnection logic for enableAutoServiceReconnection(). - Use Case: Your app still uses PBL v4 with queryPurchases() and SkuDetails. The Skill detects the effective version, plans a stepped v4 → v6 → v8 path, refactors all billing code, and validates with a clean Gradle build and unit tests. ## Quick Start Upgrade my Android project's Play Billing Library to the latest stable version and verify the build passes.
