vivreal-package-update

To update a shared dependency across multiple GitHub repositories, the Skill automates version discovery, removes node_modules and package-lock.json for a clean reinstall, and opens pull requests to streamline the merging process.

The best way to automate cross-repo dependency updates is using a workflow that bumps versions, deletes package-lock.json for a fresh reinstall, and automatically executes build and test processes to ensure integrity before opening pull requests.

To fix version skew when a shared GitHub package is updated, you can automate the discovery and update process across all repositories using that dependency, ensuring every repo pulls the new version and passes builds.

Deleting package-lock.json and node_modules before bumping dependencies ensures a fresh reinstall, which prevents stale lockfile conflicts and ensures the automated build and test processes validate the true updated dependency tree.

Yes, you can automatically create pull requests after updating dependencies across repositories. The Skill creates pull requests with the updated dependency versions to simplify the review and merging process.

Yes, this cross-repo dependency update workflow works for complex GitHub packages by automating the cumbersome and error-prone task of manually discovering and updating shared dependencies across all repositories.