一键导入
bump-version
Use when bumping the 1ONE ClaudeCode version: update package.json, run checks, branch, commit, push, create PR, wait for merge, tag release.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when bumping the 1ONE ClaudeCode version: update package.json, run checks, branch, commit, push, create PR, wait for merge, tag release.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Use this skill any time a .xlsx file is involved -- as input, output, or both. This includes: creating spreadsheets, financial models, dashboards, or trackers; reading, parsing, or extracting data from any .xlsx file; editing, modifying, or updating existing workbooks; working with formulas, charts, pivot tables, or templates; importing CSV/TSV data into Excel format. Trigger whenever the user mentions 'spreadsheet', 'workbook', 'Excel', 'financial model', 'tracker', 'dashboard', or references a .xlsx/.csv filename.
Use this skill when the user wants a .pptx with smooth cross-slide animation — PowerPoint Morph transitions, Keynote-style continuous motion, shapes that grow / move / rotate as the slide advances. Trigger on: 'morph', 'morph transition', 'smooth transition', 'continuous animation across slides', 'Keynote-style transition', 'animated slide sequence', 'shape continuity across slides'. Output is a single .pptx. This skill is a scene layer on top of officecli-pptx — inherits every pptx v2 rule (visual floor, grid, palettes, connector canon, Delivery Gate 1–5a). DO NOT invoke for a generic deck, pitch deck, or board review without cross-slide motion — route those to officecli-pptx base or officecli-pitch-deck.
Use this skill to build academic-style .docx output: journal / conference / thesis chapters carrying formal citation style (APA, Chicago, IEEE, MLA), numbered equations, figure & table cross-references, footnotes/endnotes, bibliography, or multi-column journal layout. Trigger on: 'research paper', 'journal paper', 'conference paper', 'manuscript', 'thesis', 'APA', 'MLA', 'Chicago', 'IEEE two-column', 'bibliography', 'hanging indent', 'citation style', 'abstract + keywords', 'equation numbering', 'cross-reference', paper with footnotes/endnotes. Output is a single .docx.
Use this skill any time a .docx file is involved -- as input, output, or both. This includes: creating Word documents, reports, letters, memos, or proposals; reading, parsing, or extracting text from any .docx file; editing, modifying, or updating existing documents; working with templates, tracked changes, comments, headers/footers, or tables of contents. Trigger whenever the user mentions 'Word doc', 'document', 'report', 'letter', 'memo', or references a .docx filename.
Use when executing implementation plans with independent tasks in the current session
| name | bump-version |
| description | Use when bumping the 1ONE ClaudeCode version: update package.json, run checks, branch, commit, push, create PR, wait for merge, tag release. |
Automate the 1ONE ClaudeCode version bump workflow: update version → quality checks → branch → commit → push → PR → tag.
Usage: /bump-version [version]
/bump-version 1.8.17 — bump to specified version/bump-version — auto-increment patch (e.g. 1.8.16 → 1.8.17)git branch --show-current
git status --short
main → Stop: "Please switch to main before running bump-version."git pull --rebase origin main
Fails → Stop: "Failed to pull latest code. Please resolve conflicts or network issues first."
Read package.json → extract version field.
major.minor.patch, increment patch by 1Display: "Bumping version: {current} → {target}"
Release line policy: GitHub tags follow package.json only. npm run dist:win does not bump version. After GitHub v1.22.0, main continues at 1.23.0+ (1.16.x was an internal patch line; use 1.23.0+ for public releases).
Use Edit tool to replace:
"version": "{current}""version": "{target}"bun run lint
bun run format
bunx tsc --noEmit
bunx vitest run
Fails → Stop: "Tests failed. Please fix failing tests before bumping the version."
git checkout -b chore/bump-version-{target}
git add -A
git commit -m "chore: bump version to {target}"
git push -u origin chore/bump-version-{target}
gh pr create --base main \
--title "chore: bump version to {target}" \
--body "Bump version to {target}"
Display PR URL. Then pause:
"PR created: {URL}. Please notify a team member to merge it, then confirm to continue."
Wait for user confirmation before proceeding.
git checkout main
git pull --rebase origin main
git branch -d chore/bump-version-{target}
Check if remote branch still exists:
git ls-remote --heads origin chore/bump-version-{target}
git push origin --delete chore/bump-version-{target}git tag v{target}
git push origin v{target}
Display: "Tag v{target} created and pushed. Version bump complete!"
1. Must be on clean main
2. git pull --rebase
3. Determine target version
4. Edit package.json
5. lint + format + tsc
6. vitest run
7. branch chore/bump-version-{target} → commit → push
8. gh pr create → wait for merge
9. checkout main → pull → delete branch
10. git tag v{target} && git push origin v{target}