update-dependencies

# Update Dependencies Upgrade project dependencies, researching breaking changes for major version updates. Optional filter: `$ARGUMENTS` (e.g., `react`, `Alamofire`, `serde tokio`) ## Phase 1: Review Dependencies Run the `/review-dependencies` skill to detect package managers and discover available updates. If no updates are available, stop. ## Phase 2: User Strategy Selection Present a summary showing: - Count and list of major updates (with current → target versions) - Count of minor updates - Count of patch updates Use AskUserQuestion for upgrade strategy: **Header**: "Strategy" **Options**: - **Cautious** — Upgrade minor/patch first, then major one-by-one with research - **All at once** — Research all major changes, then upgrade everything together - **Skip major** — Only upgrade minor and patch versions - **Interactive** — Ask for each major update individually ## Phase 3: Research Breaking Changes For **each package with a major version update**: ### Step 1: Calculate Version Gap Identify all major versions between current and target. For example: - `react: 17.0.2 → 19.0.0` → research v18 AND v19 breaking changes - `Alamofire: 4.9.1 → 6.0.0` → research v5 AND v6 breaking changes ### Step 2: Research Each Major Version Search for migration documentation: ``` WebSearch: "[package-name] v[X] migration guide" WebSearch: "[package-name] v[X] breaking changes" ``` Common sources: GitHub releases page, official docs, changelog files. ### Step 3: Extract Key B...