cmd-bump-package

Automate dependency version bumps and pull request creation across Vivreal repositories.

Updated May 12, 2026
One-click install
npx skills add https://github.com/HillBombCreations/vivreal-skills --skill cmd-bump-package
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmd-bump-package
Source: https://github.com/HillBombCreations/vivreal-skills/tree/main/vivreal-workflow/skills/cmd-bump-package
Command: npx skills add https://github.com/HillBombCreations/vivreal-skills --skill cmd-bump-package

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of updating shared dependencies across multiple Vivreal repositories, ensuring consistency and simplifying the workflow.

Core Features & Use Cases

  • Dependency Bumping: Automatically updates shared dependencies across Vivreal repositories.
  • Version Discovery: Identifies and proposes the latest version of a package.
  • Automated PR Creation: Generates pull requests for each repository to update the dependency version.
  • Use Case: When a new version of a shared dependency is released, use this Skill to update it across all Vivreal repositories with a single command.

Quick Start

Run the command 'bump-package <package> [target-version]' to update a specific package and its dependencies.

Frequently Asked Questions about cmd-bump-package

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically bump shared dependencies across multiple GitHub repositories?

To automatically bump shared dependencies across multiple GitHub repositories, use a dependency bumping tool that handles version discovery and creates pull requests for each repository to ensure consistency.

What is automated dependency bumping and how does it work?

Automated dependency bumping is the process of identifying the latest package version and proposing updates across multiple repositories. It works by discovering new versions and generating pull requests for each affected repository.

Do I need GitHub permissions to automate dependency bumping across repositories?

Yes, you need GitHub access and the necessary permissions to create pull requests across the target repositories to automate dependency bumping and synchronize shared package versions.

How do I update a shared package version across all my repositories at once?

To update a shared package version across repositories at once, run a dependency bumping command specifying the package and target version, which proposes updates and creates pull requests for each repository.

What is the best way to sync shared dependency versions across multiple repositories?

The best way to sync shared dependency versions across multiple repositories is using an automated dependency bumping script that discovers the latest package version and creates pull requests for each repository.