메뉴
Bump the Umbraco CMS version across all required files. Use when the user asks to bump, update, or set the version number — e.g., "bump version to 17.3.4", "set version to 18.0.0-rc", "update version". Accepts the target version as an argument.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/umbraco/Umbraco-CMS --skill umb-bump-version명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
| name | umb-bump-version |
| description | Bump the Umbraco CMS version across all required files. Use when the user asks to bump, update, or set the version number — e.g., "bump version to 17.3.4", "set version to 18.0.0-rc", "update version". Accepts the target version as an argument. |
| argument-hint | <version> (e.g., 17.3.4, 18.0.0-rc) |
Updates the Umbraco CMS version string across all files that track it.
Do NOT use AskUserQuestion if a version argument is provided. Only ask if $ARGUMENTS is empty or cannot be parsed as a version.
$ARGUMENTS - Required: the target version string (e.g., 17.3.4, 18.0.0-rc)The following 5 files must be updated with the new version:
| # | File | Field |
|---|---|---|
| 1 | version.json | "version" |
| 2 | src/Umbraco.Web.UI.Client/package.json | "version" |
| 3 | src/Umbraco.Web.UI.Client/package-lock.json | top-level "version" AND packages[""].version |
| 4 | tests/Umbraco.Tests.AcceptanceTest/package.json | "version" |
| 5 | tests/Umbraco.Tests.AcceptanceTest/package-lock.json | top-level "version" AND packages[""].version |
Note: For major version bumps (e.g., 17.x to 18.x), src/Umbraco.Web.UI.Login/package.json has a caret-ranged dependency on @umbraco-cms/backoffice (e.g., ^17.2.0) that will need manual updating. This skill does not handle that — major bumps involve many other changes beyond version strings.
Extract the version from $ARGUMENTS. It must be a valid semver-like string (e.g., 17.3.4, 18.0.0-rc, 17.4.0-preview.1). If no version is provided or it cannot be parsed, ask the user for the target version.
Read version.json and extract the current "version" value. If the current version already equals the target version, report that the version is already set and stop — do not edit, stage, or commit anything.
Otherwise, display both versions:
Bumping version: {current} -> {target}
Update each of the 5 files listed above, replacing the old version with the new version. For each file:
version.json: Replace the "version" value.package.json files: Replace the "version" value (near the top of the file).package-lock.json files: Replace BOTH the top-level "version" value AND the "version" inside the "packages": { "": { ... } } block. These are always in the first ~10 lines of the file.Use targeted edits — do NOT rewrite entire files. Be precise to avoid changing version strings in dependency entries.
After all edits, grep for the target version value across the 5 files to confirm all updates landed correctly:
grep -n "\"version\": \"{version}\"" version.json src/Umbraco.Web.UI.Client/package.json src/Umbraco.Web.UI.Client/package-lock.json tests/Umbraco.Tests.AcceptanceTest/package.json tests/Umbraco.Tests.AcceptanceTest/package-lock.json
Expect exactly 7 matches (one per package.json and version.json, two per package-lock.json).
Stage only the 5 changed files:
git add version.json src/Umbraco.Web.UI.Client/package.json src/Umbraco.Web.UI.Client/package-lock.json tests/Umbraco.Tests.AcceptanceTest/package.json tests/Umbraco.Tests.AcceptanceTest/package-lock.json
Then commit with the message Bump version to {version}. — replacing {version} with the target version:
git commit -m "Bump version to {version}."
Output a summary:
Version bumped to {version} in:
- version.json
- src/Umbraco.Web.UI.Client/package.json
- src/Umbraco.Web.UI.Client/package-lock.json
- tests/Umbraco.Tests.AcceptanceTest/package.json
- tests/Umbraco.Tests.AcceptanceTest/package-lock.json
Changes staged and committed.
Automated PR code review for Umbraco CMS. Analyzes changed files for intent, impact on consumers, breaking changes, architecture compliance, and code quality. Non-interactive — outputs a full structured review. Use this skill whenever the user asks to review a branch, review a PR, check their changes for issues, analyze a diff, or validate breaking change patterns — even if they don't say "review" explicitly. Does NOT apply to writing new code, fixing bugs, refactoring, explaining architecture, writing tests, or reviewing documentation content.
Regenerate the Management API OpenApi.json for Umbraco CMS from a running backend, and optionally regenerate the backoffice hey-api client so its generated types match. Proactively offer to run this at the end of any work that adds, removes, or changes Management API controllers, endpoints, routes, or their request/response/view models — OpenApi.json and the generated backend-api client go stale the moment the API surface changes, so suggest syncing rather than waiting to be asked. Also use it whenever the user asks to update/refresh/regenerate OpenApi.json or the openapi document, says the generated backend-api / hey-api client is stale or out of date, or has just added an endpoint and needs the client types — including phrasings like "sync the OpenAPI spec", "update the API client", "the openapi doc is out of date", or "regenerate the server API", even if OpenApi.json isn't named explicitly. Does NOT apply to Delivery API changes or to internal service/repository edits that don't alter the Management API su
Add a value summary extension so a feature's typed value can be displayed compactly in collection views (e.g., table columns). Use when a feature or property editor already has a value type and needs a renderer for collection table cells. Two variants — simple (element only, no API call) and resolver (batch API resolution needed). Prerequisite: a value type constant must already exist — use the general-add-value-type skill first if it doesn't.
SOC 직업 분류 기준
