upgrade

Pulls latest code, syncs dependencies, runs checks, applies migrations, and restarts the service.

1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/fpl0/luke --skill upgrade-fpl0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upgrade
Source: https://github.com/fpl0/luke/tree/main/.claude/skills/upgrade
Command: npx skills add https://github.com/fpl0/luke --skill upgrade-fpl0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps Luke's running deployment up to date by pulling the latest code, applying changes to data, and restarting services when upgrades are requested.

Core Features & Use Cases

  • Pull the latest Luke code and sync dependencies to ensure the running instance matches the repo.
  • Run type checks, lint, and necessary migrations to safely upgrade schemas, persona, and launch configuration.
  • Use case: when you say upgrade or update Luke, or after code changes that must reach the live agent.

Quick Start

Use the upgrade command to pull latest code, apply migrations, restart the service, and verify the running instance.

Frequently Asked Questions about upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code deployment and apply migrations to update a live service?

Automate code deployment by pulling the latest code, syncing dependencies, running checks, applying migrations, and restarting the service to ensure the live instance matches the repository.

What steps are required to safely upgrade schemas and sync dependencies during a deployment?

Safely upgrade schemas by running type checks, linting, and necessary migrations after pulling code, ensuring dependencies sync correctly before restarting the service.

When do I need to run migrations and restart the service after pulling code changes?

Run migrations and restart the service whenever code changes must reach the live agent, such as after requesting an upgrade or updating schemas, persona, or launch configuration.

Does this upgrade automation handle type checks and lint before restarting the service?

Yes, the upgrade automation runs type checks and lint as deterministic safety checks before applying migrations and restarting the service.

What's the best way to keep a running deployment up to date after code changes?

The best way to keep a running deployment up to date is to pull the latest code, sync dependencies, apply migrations, and restart the service to verify the running instance.

Can I update persona and launch configuration automatically during a service upgrade?

Yes, you can update persona and launch configuration automatically by applying necessary migrations during the upgrade process before restarting the live service.