Agent Skills › voidzero-dev/vite-plus › sync-upstream-dependency-docs

sync-upstream-dependency-docs

GitHub

同步Vite+文档中嵌入的上游依赖精确版本，确保README、CLI指南等文档中的版本号与当前捆绑版本一致。

.claude/skills/sync-upstream-dependency-docs/SKILL.md voidzero-dev/vite-plus

Trigger Scenarios

上游依赖（如Vite, Vitest）版本发生变更后需要更新文档中的精确版本号以匹配当前包版本时

Install

npx skills add voidzero-dev/vite-plus --skill sync-upstream-dependency-docs -g -y

More Options

Non-standard path

npx skills add https://github.com/voidzero-dev/vite-plus/tree/main/.claude/skills/sync-upstream-dependency-docs -g -y

Use without installing

npx skills use voidzero-dev/vite-plus@sync-upstream-dependency-docs

指定 Agent (Claude Code)

npx skills add voidzero-dev/vite-plus --skill sync-upstream-dependency-docs -a claude-code -g -y

安装 repo 全部 skill

npx skills add voidzero-dev/vite-plus --all -g -y

预览 repo 内 skill

npx skills add voidzero-dev/vite-plus --list

SKILL.md

Frontmatter

{
    "name": "sync-upstream-dependency-docs",
    "description": "Sync exact upstream dependency versions embedded in Vite+ documentation after the automated dependency upgrade. Use when bundled Vite, Vitest, Oxlint, Oxfmt, tsdown, Rolldown, or related package versions change.",
    "allowed-tools": "Read, Grep, Glob, Edit, Bash"
}

Sync upstream dependency docs

Read $UPGRADE_DEPS_META_DIR/versions.json and consider only entries whose old and new values differ.
Search README.md, packages/*/README.md, and docs/**/*.md for each changed package name and its old exact version. Do not treat changelogs, RFC examples, snapshots, or broad ranges such as vitest@4.x as current-version references.
Update references that promise to match Vite+'s currently bundled version. In particular, keep every exact Vitest pin in the manual-installation examples in docs/guide/local-cli.md, README.md, and packages/cli/README.md in sync. Project-local upgrade guidance lives in docs/guide/upgrade-project.md; docs/guide/upgrade.md covers global CLI upgrades.
Preserve the surrounding wording and formatting. Do not rewrite examples whose version is intentionally historical or illustrative.
Re-run the searches for the changed packages and inspect the focused diff. No stale exact version may remain in documentation that describes the current bundle.