bump-vite-task

Update vite-task git dependencies across Rust workspace crates to the latest main commit.

3|1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/wfvue/SynapSH --skill bump-vite-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bump-vite-task
Source: https://github.com/wfvue/SynapSH/tree/main/.agent/skills/bump-vite-task
Command: npx skills add https://github.com/wfvue/SynapSH --skill bump-vite-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates keeping vite-task dependencies up-to-date across a multi-crate Rust workspace by pulling in the latest main commit and updating related Cargo.toml entries.

Core Features & Use Cases

  • Detect and read the current vite-task revision from Cargo.toml entries across crates: fspy, vite_glob, vite_path, vite_str, vite_task, vite_workspace.
  • Fetch latest commit on the vite-task main branch and verify its availability.
  • Update all references in Cargo.toml to the new revision and ensure CI can clone upstream dependencies.
  • Validate changes with cargo check and targeted tests, and prepare a PR with a clear changelog reference.
  • Use case: When a breaking change in vite-task requires synchronization across the workspace without manual edits.

Quick Start

Update the vite-task revision to the latest main commit and open a PR with the changes.

Frequently Asked Questions about bump-vite-task

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

FAQPage Schema
How do I update git dependencies in a Rust workspace to the latest main commit?

To update git dependencies across a Rust workspace, this Skill reads current revisions from Cargo.toml, fetches the latest main commit from the vite-task repository, and patches all occurrences across crates like fspy, vite_glob, vite_path, vite_str, vite_task, and vite_workspace.

What is the best way to bump vite-task revisions across multiple crates without manual edits?

Bumping vite-task revisions is automated by detecting current entries in Cargo.toml across crates, fetching the latest main commit, patching all references, and validating changes with cargo check and tests to ensure compatibility.

Does this dependency bumping process validate workspace compatibility after updating Cargo.toml?

Yes, the dependency bumping process validates workspace compatibility by running cargo check and targeted tests after patching all Cargo.toml references to the new vite-task revision.

Can I use this to synchronize a breaking change in vite-task across my Rust workspace?

Yes, you can use this to synchronize breaking changes by pulling in the latest main commit of vite-task, updating related Cargo.toml entries across all crates, and preparing a PR with a clear changelog reference.

Why does updating a git dependency in Cargo.toml require checking upstream crates?

Updating a git dependency requires checking upstream crates because the workspace references vite-task indirectly through crates like fspy, vite_glob, vite_path, vite_str, vite_task, and vite_workspace, ensuring CI can clone all necessary dependencies.

What limitations should I expect when bumping vite-task in a Rust workspace?

Limitations include that this process applies specifically to Rust workspace projects referencing vite-task indirectly through the listed crates, and it requires upstream dependencies to be present for CI cloning and validation.