laravel-upgrade skillA
laravel-upgrade is agent-read markdown (skill) from majdghithan/agent-skills: Upgrade a Laravel application across major versions safely (Laravel 8 -> 9 -> 10 -> 11 -> 12 -> 13), one hop at a time. Use when upgrading Laravel, when a `composer update` fails after a major bump, when deciding whether to hop versions by hand or pay for Laravel Shift, or when something compiled fine but broke at runtime after an upgrade. Detects the current version from composer.json, then loads only the hop guides you need. Focuses on the runtime bites the official upgrade guide underplays, n.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Laravel: version upgrades (8 -> 13)
Laravel's own upgrade guides at `laravel.com/docs/{ver}/upgrade` are genuinely good and list every mechanical rename. This skill does NOT repeat them. It carries the two things the docs and Shift do not give you: **the runtime bites that pass compilation and break later**, and **the judgment call of whether to hand-upgrade or pay Shift to do it.**
## The three rules that prevent a bad upgrade
1. **PHP first, framework second.** Every major has a hard PHP floor. Bump and deploy the PHP version on its own, confirm the app runs green on the new PHP under the *old* Laravel, then upgrade Laravel. Doing both at once means you cannot tell which one broke.
2. **Hop, never leap.** Upgrade one major at a time (10 -> 11 -> 12, not 10 -> 12). Each hop's guide assumes you came from the one before it. The exception is Shift, which chains hops for you.
3. **Tests are the upgrade plan.** If the suite is thin, the "bites" below are what bites you in production instead. Before a multi-version upgrade, add feature tests on the money/auth/critical paths first. No suite -> upgrade one hop, exercise the app hard, then the next.
…Read the whole file at its exact version.
How to install
mdr add majdghithan/agent-skills/laravel-upgrade@git:20260729.4bed2camdr add majdghithan/agent-skills/laravel-upgrade@sha256:9ff6e404f72fe020Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_zg6q4e7v5bcwkkb5)
1 badge views in 30 days
Versions
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 (6496 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
majdghithan/agent-skills · 7 stars · license MIT · pushed 2026-09-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zg6q4e7v5bcwkkb5 GET https://markdownregistry.com/api/v1/resolve?ref=majdghithan/agent-skills/laravel-upgrade GET https://markdownregistry.com/api/v1/blob/9ff6e404f72fe020e07feb805af00a5e8d0c033694adf7bca6d4a6d9dcbf2b2f
Your agent 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.