Skip to content
Skills Library
Programming · Automation

update-xperience

/update-xperience

Updates an Xperience by Kentico project to a newer version. Use when the user wants to update or upgrade their Xperience by Kentico project, apply a hotfix, or move to a newer refresh.

Licence
MIT
Last repository change
14.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 14.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Updates an Xperience by Kentico project to a newer version. Use when the user wants to update or upgrade their Xperience by Kentico project, apply a hotfix, or move to a newer refresh.

Arguments

/update-xperience [target-version]
Original author description

Updates an Xperience by Kentico project to a newer version. Use when the user wants to update or upgrade their Xperience by Kentico project, apply a hotfix, or move to a newer refresh.

How it works

  1. Workflow
Original SKILL.md headings · 37 lines, 315 words
SKILL.md preview
---
name: "update-xperience"
description: "Updates an Xperience by Kentico project to a newer version. Use when the user wants to update or upgrade their Xperience by Kentico project, apply a hotfix, or move to a newer refresh."
argument-hint: "[target-version]"
compatibility: "Requires Kentico Docs MCP"
---

You are tasked with updating an Xperience by Kentico project to a newer version. The official release notes and update documentation are the source of truth — follow them, do not invent update steps.

## Workflow

### 1. Determine the versions

- Identify the current version from the `Kentico.Xperience.*` NuGet package references in the project.
- Identify the target version: use the version passed as an argument if provided, otherwise the latest available.

### 2. Review the release notes

- Read the release notes in the [Changelog](https://docs.kentico.com/changelog) for **every version between the current and target version**.
- Note breaking changes, deprecations, new object types for CI/CD, and any manual steps.
- **Follow the pages linked from the release notes** that guide through specific feature updates — they contain the instructions for adapting the project.

### 3. Follow the official update procedure

- Read `references/update-docs.md` and fetch the relevant documentation pages.
- Perform the update as documented — do not substitute your own procedure or external tools; everything needed (including CI handling) is built into the product's CLI.

### 4. Resolve breaking changes and obsolete API

- Apply the code and configuration changes required by the release notes and their linked guides.
- Build the solution and fix remaining errors caused by the update.
- After the build succeeds, resolve obsolete-API warnings: migrate the affected code to the replacements described in the obsolete warning messages.

### 5. Update CI/CD repository configuration

- If the project uses the `IncludedObjectTypes` element in a CI or CD `repository.config`, collect the **New object types for CI/CD** entries from the release notes of every version in the update path.
- Add the new object types the project should include to the allowlist, per the official update documentation.

### 6. Verify and report

- Verify the result (build, tests if present).
- Summarize what was updated and which release-note items required action.
Files in this package (2)
  • SKILL.md 2 KB
  • references/update-docs.md 1 KB

Versions

RepositoryScoreLicence
This page · kentico/xperience-by-kentico-kenticopilot90MIT
Kentico/repo-template-xperience100MIT

Database snapshot: 13.11.2026 · package version 543cc0d4eee2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100migrate-code-page
    Migrates a page from a Kentico Xperience 13 project to Xperience by Kentico. Converts controllers, views, layouts, content retrieval, and all dependencies for the specified page. Use when migrating the business and presentation logic of a specific page after its Page Builder…
  • 100migrate-code-global
    Migrates global code from a Kentico Xperience 13 project to Xperience by Kentico. Sets up the target project structure, generates code files, and migrates shared code including localization, styles, business logic, and project startup configuration. Use when starting a KX13 to…
  • 96lab-update
    Update a byolab lab to a newer release without touching the owner's work. Use when the owner asks to update, upgrade, pull the latest byolab, or asks what changed in a new version.
  • 100upgrade
    Upgrade an existing Magento 2 module to a newer Magento version, newer PHP version, or newer framework dependency. Use when the user wants to bump Magento support, update PHP constraints, replace deprecated API usage, or scan for and remediate BC breaks. Drives: deprecation scan…
  • 100upgrade-microbus
    TRIGGER when the user asks to upgrade the project to a newer or the latest version of Microbus, or to update the framework. Each Microbus release ships this one self-contained skill; it applies that release's single-version migration, then chains to the next release's copy of…
  • 100upgrade-react-native
    Use when upgrading react-native to a newer version. Handles version bumps, native project changes (Android/iOS), dependency updates, and breaking change migration. Invoke with `/upgrade-react-native <version>`.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.