bump-deps

Bump Dependencies

Analyze outdated dependencies and safely upgrade them with breaking change detection.

Workflow

1. Detect package manager based on current directory:

   • If in frontend/ directory or working with TypeScript/JavaScript: use pnpm reference
   • If in backend/ directory or working with Python: use uv reference

2. List outdated dependencies using the package manager-specific command from the reference

3. Spawn background analysis tasks for EACH notable upgrade:

   CRITICAL: You MUST spawn the package-upgrade-analyzer sub-agent as a background Task for EACH and EVERY notable upgrade. Do NOT take shortcuts.

   Task(
     subagent_type="package-upgrade-analyzer",
     run_in_background=true,
     prompt="Analyze upgrade for {package_name} from {old_version} to {new_version}. GitHub: {repo_url}"
   )
   

   Notable upgrades include:

   • Major version bumps (e.g., v4 → v5)
   • Packages with known breaking changes
   • Core dependencies (React, Next.js, FastAPI, SQLAlchemy, etc.)

   Spawn ALL tasks in a single message with multiple tool calls for maximum parallelism.

4. Wait for all background tasks to complete:

   • Use TaskOutput to retrieve results from each background task
   • Once ALL tasks are complete, ultrathink about the suggestions, migration guides, and release notes
   • Invoke the Plan tool and its sub-agents to strategically address the breaking changes
   • Plan carefully to maintain as much of the original behavior as possible

5. Ask clarifying questions:

   • If the migration path forward is ambiguous, ASK questions
   • Do NOT proceed unless you're sure about the safety of the dependency version bumps

6. Generate PR summary document:

   Write a .claude/scratchpad/PR.md file using the PR template. Ensure that all package identifiers are properly wrapped in backticks for readability.