How do I install the Kirby Upgrade And Maintenance skill?

Run npx skillmds@latest add majiayu000/kirby-upgrade-and-maintenance in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Kirby Upgrade And Maintenance safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kirby Upgrade And Maintenance?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kirby Upgrade And Maintenance free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Kirby Upgrade And Maintenance?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kirby Upgrade And Maintenance by majiayu000

Name: Kirby Upgrade And Maintenance
Rating: 4.2 (5 reviews)
Author: majiayu000

Kirby Upgrade And Maintenance

Upgrades Kirby and maintains dependencies safely using composer audit, plugin compatibility checks, and official docs. Use when updating Kirby versions or making maintenance changes that affect runtime.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

Kirby Upgrade and Maintenance

Quick start

Follow the workflow below for safe, incremental upgrades.

KB entry points

kirby://kb/panel/compat-k5-k6-migration
kirby://kb/panel/tooling-kirbyup
kirby://kb/glossary/kirbyup
kirby://kb/glossary/plugin

Required inputs

Current and target Kirby versions.
Environment constraints and downtime tolerance.
Plugin compatibility risks and rollback expectations.

Default upgrade checklist

Read the target version guide and note breaking changes.
Update composer.json constraints, then review the lockfile diff.
Run project scripts and render representative pages.
Verify runtime commands and CLI version match.

Rollback note

Keep a copy of the previous composer.lock and vendor/ state.

Rollback checklist

Restore the previous composer.lock.
Reinstall dependencies and re-run smoke tests.
Re-render representative pages to confirm behavior.

Staged upgrade pattern

Upgrade a single environment/site first, then roll out to others.
Validate plugins and custom code before multi-site rollout.

Common pitfalls

Skipping plugin compatibility checks.
Upgrading multiple major versions in one jump.

Workflow

Call kirby:kirby_init or gather baseline data with kirby:kirby_info and kirby:kirby_composer_audit.
Inventory plugins for compatibility risks: kirby:kirby_plugins_index.
Use kirby:kirby_online to find official upgrade guides and breaking changes for the target version (prefer kirby:kirby_search first).
Build a project-specific checklist of required code/config changes.
Ask for confirmation before dependency updates that change the lockfile.
Verify:
- run project scripts discovered in the composer audit
- call kirby:kirby_cli_version to confirm the installed version
- ensure runtime commands are in sync: kirby:kirby_runtime_status and kirby:kirby_runtime_install if needed
- render representative pages with kirby:kirby_render_page(noCache=true)
Summarize changes, remaining risks, and a short manual QA checklist.

---name: kirby-upgrade-and-maintenancedescription: Upgrades Kirby and maintains dependencies safely using composer audit, plugin compatibility checks, and official docs. Use when updating Kirby versions or making maintenance changes that affect runtime.--- # Kirby Upgrade and Maintenance ## Quick start - Follow the workflow below for safe, incremental upgrades. ## KB entry points - `kirby://kb/panel/compat-k5-k6-migration` - `kirby://kb/panel/tooling-kirbyup` - `kirby://kb/glossary/kirbyup` - `kirby://kb/glossary/plugin` ## Required inputs - Current and target Kirby versions. - Environment constraints and downtime tolerance. - Plugin compatibility risks and rollback expectations. ## Default upgrade checklist - Read the target version guide and note breaking changes. - Update `composer.json` constraints, then review the lockfile diff. - Run project scripts and render representative pages. - Verify runtime commands and CLI version match. ## Rollback note - Keep a copy of the previous `composer.lock` and `vendor/` state. ## Rollback checklist - Restore the previous `composer.lock`. - Reinstall dependencies and re-run smoke tests. - Re-render representative pages to confirm behavior. ## Staged upgrade pattern - Upgrade a single environment/site first, then roll out to others. - Validate plugins and custom code before multi-site rollout. ## Common pitfalls - Skipping plugin compatibility checks. - Upgrading multiple major versions in one jump. ## Workflow 1. Call `kirby:kirby_init` or gather baseline data with `kirby:kirby_info` and `kirby:kirby_composer_audit`. 2. Inventory plugins for compatibility risks: `kirby:kirby_plugins_index`. 3. Use `kirby:kirby_online` to find official upgrade guides and breaking changes for the target version (prefer `kirby:kirby_search` first). 4. Build a project-specific checklist of required code/config changes. 5. Ask for confirmation before dependency updates that change the lockfile. 6. Verify: - run project scripts discovered in the composer audit - call `kirby:kirby_cli_version` to confirm the installed version - ensure runtime commands are in sync: `kirby:kirby_runtime_status` and `kirby:kirby_runtime_install` if needed - render representative pages with `kirby:kirby_render_page(noCache=true)` 7. Summarize changes, remaining risks, and a short manual QA checklist.

Frequently asked questions