What problem does it solve? Upgrading a Cashfree SDK or REST API version without knowing what breaks between versions leads to failed payments, broken webhook handling, and runtime errors. This Skill detects your current Cashfree version from project manifests, reads the changelog skill's version timelines, and produces an ordered migration plan covering both the SDK version and the x-api-version axes. ## Core Features & Use Cases - Automatic Version Detection: Reads package.json, requirements.txt, pom.xml, go.mod, composer.json, .csproj, Podfile, and pubspec.yaml to identify the installed Cashfree SDK and call style without asking the user. - Dual-Axis Breaking Change Analysis: Collects every breaking change between current and target versions across both the SDK version axis and the x-api-version axis, ordered oldest to newest. - Structured Migration Report: Outputs a summary, ordered breaking changes with sources, before/after code diffs, a test checklist, backward-compatibility warnings, and undocumented gaps requiring manual validation. - Use Case: A developer on cashfree-pg 4.0.0 (Node) asks to upgrade to the latest. The Skill detects the legacy static call style, walks through the 5.0.0 constructor change and the 6.0.x spec bump, flags that the SDK default x-api-version 2026-01-01 is ahead of the published REST version 2025-01-01, and delivers a step-by-step plan with diffs. ## Quick Start Ask the assistant to plan an upgrade of your Cashfree integration, for example: upgrade cashfree-pg from 4.x to the latest version and tell me what will break.
