Power Update Invoker

Check for available updates across all project dependencies, runtime versions, and tools, then apply selected updates with compatibility verification and rollback support.

When to Use This Command

Run this command when...

• You want to check for available updates across all packages, runtimes, and development tools in your project
• You need to selectively apply updates with automatic compatibility testing before finalizing changes
• You want to update a specific package to its latest version with dependency resolution and conflict detection
• You need to batch-update all packages within their semver-compatible ranges safely
• You want a report of all outdated dependencies with changelogs and breaking change warnings

Quick Start

Copy
# .claude/commands/power-update-invoker.yaml
name: Power Update Invoker
description: Check and apply dependency updates with compatibility verification
inputs:
  - name: scope
    description: "all, major, minor, patch, or specific package name"
    default: "minor"

Copy
# Check for all available updates
claude "power-update-invoker --scope all --dry-run"

# Apply minor and patch updates safely
claude "power-update-invoker --scope minor"

# Update a specific package
claude "power-update-invoker react@latest"

Output:
  [scan] Checking 142 dependencies for updates...
  Available Updates:
    Major (breaking): 3 packages
    Minor (features): 8 packages
    Patch (fixes):    12 packages

  [apply] Updating 20 minor + patch packages...
  [test] Running test suite... 142 passed, 0 failed
  [verify] Build check... success
  Done. 20 packages updated. 3 major updates pending review.

Core Concepts

Concept	Description
Update Classification	Groups updates by semver category: major (breaking), minor (features), patch (bug fixes)
Compatibility Testing	Runs tests and build after applying updates to verify nothing breaks before committing
Selective Application	Apply all patches, all minors, or specific packages rather than updating everything at once
Changelog Surfacing	Shows relevant changelog entries for each update so you can assess impact before applying
Rollback Support	Preserves the original lock file so updates can be reverted if issues are discovered later

Update Pipeline:
  ┌──────────┐   ┌──────────┐   ┌──────────┐   ┌──────────┐
  │  Scan    │──>│ Classify │──>│  Apply   │──>│  Test    │
  │ Outdated │   │ by Semver│   │ Updates  │   │ & Build  │
  └──────────┘   └──────────┘   └──────────┘   └────┬─────┘
                                                     │
                                          pass/      │     \fail
                                        ┌──────┐     │    ┌────────┐
                                        │Commit│     │    │Rollback│
                                        └──────┘     │    └────────┘

Configuration

Parameter	Type	Default	Description
scope	string	"minor"	Update scope: all, major, minor, patch, or a specific package name
dry_run	boolean	false	Show available updates without applying any changes
test	boolean	true	Run the test suite after applying updates to verify compatibility
build	boolean	true	Run the build step after tests to catch compilation errors
interactive	boolean	false	Prompt for confirmation before each major version update

Best Practices

1. Apply patch updates frequently -- Patch updates contain bug fixes and security patches. Apply them weekly to stay current without risking breaking changes.
2. Review major updates individually -- Major version updates include breaking changes. Update one major package at a time, read the migration guide, and run the full test suite.
3. Use dry-run before applying -- Preview available updates with --dry-run to assess the scope of changes before any packages are modified.
4. Keep the lock file committed -- After successful updates, commit the updated lock file so all team members and CI environments use the same versions.
5. Schedule update sessions -- Dedicate time regularly (weekly for patches, monthly for minors) rather than letting updates accumulate into a large, risky batch.

Common Issues

1. Peer dependency conflicts -- Updating one package may conflict with another package's peer dependency requirements. Read the error message to identify which packages need coordinated updates.
2. Tests pass but runtime fails -- Some breaking changes are not caught by tests. After updating, test the application manually in a staging environment before deploying.
3. Lock file merge conflicts -- Multiple developers updating packages simultaneously creates lock file conflicts. Coordinate updates through a single branch or designate one person for dependency updates.