菜单
Consistently bump and synchronize versions across all packages in the monorepo using pnpm. Use this to ensure the root and all workspace packages share the same version number.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run comprehensive integration tests using real skills (Vercel, Anthropic, Expo) in a Docker container. Managed via Makefile for standard lifecycle control.
Synchronize technical sections in README.md and CONTRIBUTING.md with the actual project state.
Run linters and fix violations, formatting errors, or style mismatches using Trunk. Use when code quality checks fail, before submitting PRs, or to repair "broken" linting states.
Build the project and automatically fix any build errors, compilation failures, or type mismatches. Use when the project fails to build, shows "broken" states, or after making significant changes.
Perform a "hard reset" of the development environment. Use when dependencies are corrupted, lockfiles are out of sync, or environment tools (Trunk/pnpm) are in an inconsistent state.
Fix a GitHub issue end-to-end. Use when given an issue number to fix, implementing bug fixes, or addressing reported problems.
| name | bumpup-versions |
| description | Consistently bump and synchronize versions across all packages in the monorepo using pnpm. Use this to ensure the root and all workspace packages share the same version number. |
This skill provides a standardized workflow to synchronize and increment version numbers across the entire monorepo (root and all packages) using native pnpm commands.
package.json and workspace packages.Identify if you are performing a semantic bump (patch, minor, major) or setting an explicit version (e.g., 1.0.0).
Run the version command recursively across all packages in the workspace using pnpm -r exec. The --no-git-tag-version flag prevents automatic git tagging and commits, and --allow-same-version ensures it doesn't fail if a package is already at the target version.
pnpm -r exec pnpm version <version_or_bump_type> --no-git-tag-version --allow-same-version
Update the root package.json to match the workspace versions.
pnpm version <version_or_bump_type> --no-git-tag-version --allow-same-version
Run pnpm install to ensure pnpm-lock.yaml is updated with the new versions and any internal workspace dependencies (using workspace:*) are correctly resolved.
pnpm install
Check a sample of package.json files to ensure they all reflect the new version.
grep '"version":' package.json packages/*/package.json packages/plugins/*/package.json
version field in the root package.json matches the target version.version field in all packages/**/package.json files matches the target version.pnpm-lock.yaml has been updated and there are no linting/test regressions related to the version change.pnpm -r exec pnpm version patch --no-git-tag-version --allow-same-versionpnpm version patch --no-git-tag-version --allow-same-versionpnpm installgrep '"version":' package.json packages/*/package.jsonpnpm -r exec pnpm version 0.2.0 --no-git-tag-version --allow-same-versionpnpm version 0.2.0 --no-git-tag-version --allow-same-versionpnpm install