major-upgrade SKILL.md skillA
major-upgrade from mattbrailsford/umbraco-devkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mattbrailsford/umbraco-devkit/major-upgrade@git:20261016.a78a902Pins git:20261016.a78a902 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mattbrailsford/umbraco-devkit
- Path
plugins/umbraco-devkit/skills/major-upgrade/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261016.a78a902, committed Oct 16, 2026
- First version recorded
- Oct 14, 2026
- Size
- 22,975 bytes
- Repository stars
- 3
- License
- MIT
Moves an Umbraco package to a new CMS major (for example 17 to 18): finds the breaking changes that hit it, writes an ordered checklist in `docs/upgrades/v<major>.md`, and works through it with the builder and reviewer agents. Use for "upgrade to Umbraco N", "support v18", a new major's beta or RC, or moving from one RC to the next. Not for minor or patch bumps.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# major-upgrade A CMS major upgrade is the same features on a new base, so the `feature-explore` → `feature-design` → `feature-plan` pipeline doesn't fit it, and it's far too big for `quick-fix`. This skill is its own lane: it plans the upgrade from Umbraco's published breaking changes, then builds it with the same builder → reviewer → smoke → commit gate as `feature-build`. ## Scope - IN: one hop to one target major. Dependency and target framework bumps, code changes forced by breaking changes or removed obsolete APIs, the frontend's `@umbraco-cms/backoffice` bump, the package's own compatibility markers (version, dependency range, marketplace metadata, README), and the third-party dependency bumps the user picks from inventory step 10. - OUT: new features, refactors the upgrade doesn't force, and dropping an older major the project still supports. Note those in the upgrade file's "Follow-ups" section instead. Releasing the upgraded package is also out of scope; it's the project's own release steps. ## Argument `$ARGUMENTS` is the target major (`18`, `v18`). If empty, ask. **First run or refresh?** If `docs/upgrades/v<major>.md` already exists, an earlier run …
Read the whole file at its exact version.
How to install
mdr add mattbrailsford/umbraco-devkit/major-upgrade@sha256:59a6bedbc3bc733eThe line at the top of this page pins the label git:20261016.a78a902, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_4aavzs2whkhzrex5)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 14, 2026 and Oct 16, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.a78a902 latest | 2026-10-16 | a78a902 | 22,975 B | A | view · diff |
| git:20261015.5a5859e | 2026-10-15 | 5a5859e | 23,303 B | A | view · diff |
| git:20261015.f4e1fe0 | 2026-10-15 | f4e1fe0 | 23,289 B | A | view · diff |
| git:20261015.0ed244b | 2026-10-15 | 0ed244b | 23,286 B | A | view · diff |
| git:20261014.87385e6 | 2026-10-14 | 87385e6 | 20,199 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (22975 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
mattbrailsford/umbraco-devkit · 3 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4aavzs2whkhzrex5 GET https://markdownregistry.com/api/v1/resolve?ref=mattbrailsford/umbraco-devkit/major-upgrade GET https://markdownregistry.com/api/v1/blob/59a6bedbc3bc733ea08516dd380f5d0a075de83b5b8c58c62d9947a2dc687c08
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.