SkillsAdd

smithery/bnomei

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.

Installation

$ npx skills add smithery/bnomei --skill kirby-upgrade-and-maintenance
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

crm-maintenance Similar name
anthropics/knowledge-work-plugins

Keeps HubSpot current without the owner opening it: creates and updates contacts and deals from…

1.4K installs
k6-test-maintenance Similar name
grafana/skills

Maintain and improve existing k6 test scripts. Covers threshold tightening based on trend data,…

1.3K installs
account-maintenance Similar name
joellewis/finance_skills

Process account maintenance requests across the account lifecycle. Use when changing a client a…

523 installs
changelog-maintenance Similar name
aj-geddes/useful-ai-prompts

Maintain comprehensive changelogs and release notes following Keep a Changelog format. Use when…

482 installs
story-maintenance Similar name
danjdewhurst/story-skills

This skill should be used when the user asks to validate, reindex, repair registries, check lin…

1 installs
changelog-maintenance Similar name
akillness/jeo-skills

Write and maintain release-history artifacts for shipped changes: `CHANGELOG.md` updates, relea…

357 installs

Also in this package

Other skills from smithery/bnomei · top by installs.

npx skills add smithery/bnomei
kirby-security-and-auth 0 kirby-project-tour 0 kirby-plugin-development 0 kirby-performance-and-media 0 kirby-panel-and-blueprints 0 kirby-ide-support 0 kirby-i18n-workflows 0 kirby-headless-api 0 kirby-forms-and-frontend-actions 0 kirby-debugging-and-tracing 0

Browse all from smithery/bnomei

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,372 B
  • docs SUMMARY.md 239 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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:kirbyinit or gather baseline data with kirby:kirbyinfo and kirby:kirbycomposeraudit.
  2. Inventory plugins for compatibility risks: kirby:kirbypluginsindex.
  3. Use kirby:kirbyonline to find official upgrade guides and breaking changes for the target version (prefer kirby:kirbysearch 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:kirbycliversion to confirm the installed version - ensure runtime commands are in sync: kirby:kirbyruntimestatus and kirby:kirbyruntimeinstall if needed - render representative pages with kirby:kirbyrenderpage(noCache=true)

  1. Summarize changes, remaining risks, and a short manual QA checklist.