How do I install the Sync Upstream CLI Help skill?

Run npx skillmds@latest add voidzero-dev/sync-upstream-cli-help in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sync Upstream CLI Help safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sync Upstream CLI Help?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sync Upstream CLI Help free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sync Upstream CLI Help?

voidzero-dev (@voidzero-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sync Upstream CLI Help by voidzero-dev

Name: Sync Upstream CLI Help
Author: voidzero-dev

File contents

Sync upstream CLI help

Input and target

Read the diff from $CLI_HELP_DIFF_REPORT; first run test -r "$CLI_HELP_DIFF_REPORT". Act only when $CLI_HELP_DIFF_CHANGED is true.
Treat the upgraded tool's --help output as the source of truth. The report locates changes and versions; rerun the exact version when its diff is truncated.
Edit commandHelpDocs in packages/cli/src/help.ts.
Do not edit packages/cli/src/utils/help.ts for content drift. It owns terminal wrapping, alignment, and the right margin.

Upstream help	Document entry
`vite --help`	`dev`
`vite build --help`	`build`
`vite preview --help`	`preview`
`vitest --help`	`test`
`oxlint --help`	`lint`
`oxfmt --help`	`fmt`
`tsdown --help`	`pack`

Change

For items Vite+ exposes, copy upstream labels, descriptions, section titles, and section guidance exactly. Preserve intentional lines and lists, but not terminal padding, automatic wrapping, ANSI color, or version banners.
Remove an upstream item only after confirming Vite+ no longer supports or deliberately retains it.

Do not change

Keep Vite+-owned usage, summaries, examples, and documentation URLs.
Keep config selectors/loaders hidden, including --config, --configLoader, and --disable-nested-config.
Do not add standalone modes such as --init, --migrate, or --lsp, top-level --version, or options Vite+ does not forward.
Do not change runtime forwarding or rewrite upstream wording for a Vite+-specific runtime default. Use sync-tsdown-cli for tsdown runtime changes.

Re-record the affected CLI help snapshots and inspect their diffs. Do not modify help documents when the report contains no actionable exposed change.

---name: sync-upstream-cli-helpdescription: Sync Vite+'s static CLI help with Vite, Vitest, Oxlint, Oxfmt, and tsdown while preserving intentional omissions. Use when an upstream dependency upgrade changes CLI help.---# Sync upstream CLI help## Input and target- Read the diff from `$CLI_HELP_DIFF_REPORT`; first run `test -r "$CLI_HELP_DIFF_REPORT"`. Act only when `$CLI_HELP_DIFF_CHANGED` is `true`.- Treat the upgraded tool's `--help` output as the source of truth. The report locates changes and versions; rerun the exact version when its diff is truncated.- Edit `commandHelpDocs` in `packages/cli/src/help.ts`.- Do not edit `packages/cli/src/utils/help.ts` for content drift. It owns terminal wrapping, alignment, and the right margin.| Upstream help | Document entry || --------------------- | -------------- || `vite --help` | `dev` || `vite build --help` | `build` || `vite preview --help` | `preview` || `vitest --help` | `test` || `oxlint --help` | `lint` || `oxfmt --help` | `fmt` || `tsdown --help` | `pack` |## Change- For items Vite+ exposes, copy upstream labels, descriptions, section titles, and section guidance exactly. Preserve intentional lines and lists, but not terminal padding, automatic wrapping, ANSI color, or version banners.- Remove an upstream item only after confirming Vite+ no longer supports or deliberately retains it.## Do not change- Keep Vite+-owned usage, summaries, examples, and documentation URLs.- Keep config selectors/loaders hidden, including `--config`, `--configLoader`, and `--disable-nested-config`.- Do not add standalone modes such as `--init`, `--migrate`, or `--lsp`, top-level `--version`, or options Vite+ does not forward.- Do not change runtime forwarding or rewrite upstream wording for a Vite+-specific runtime default. Use `sync-tsdown-cli` for tsdown runtime changes.Re-record the affected CLI help snapshots and inspect their diffs. Do not modify helpdocuments when the report contains no actionable exposed change.

Frequently asked questions

Sync Upstream CLI Help