orbit-life-upgrade

Detect schema changes and validate idempotent migrations during plugin version upgrades.

2|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/adityaarsharma/orbit --skill orbit-life-upgrade
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: orbit-life-upgrade
Source: https://github.com/adityaarsharma/orbit/tree/main/skills/orbit-life-upgrade
Command: npx skills add https://github.com/adityaarsharma/orbit --skill orbit-life-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

šŸ’” This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies potential issues in migration logic during plugin version upgrades, such as schema changes, ensuring idempotency and full migration coverage.

Core Features & Use Cases

  • Schema and Option Shape Detection: Identifies plugins that change their schema or option shape between versions.
  • Migration Path Verification: Ensures that migrations run once and are idempotent, with full coverage of every n→n+1 path.
  • Version-tracking Option Validation: Checks for the existence of a version-tracking option in the plugin.
  • Data Integrity Protection: Ensures data migration integrity between version upgrades.
  • Use Case: Use this Skill when preparing for a version upgrade to detect any potential issues in the migration logic and prevent data corruption.

Quick Start

Run the skill to audit the version-upgrade migration logic for your plugin, ensuring that all schema changes and data migrations are correctly handled.

Frequently Asked Questions about orbit-life-upgrade

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

FAQPage Schema
How do I ensure database migrations are idempotent during a plugin version upgrade?ā–¼

Idempotent migrations during a plugin version upgrade are ensured by verifying that migration logic runs once and maintains data integrity across all schema changes. This Skill audits your version-tracking code to confirm migrations execute predictably without duplicating data modifications.

What is the best way to verify full coverage of migration paths between plugin versions?ā–¼

Full coverage of migration paths is verified by analyzing version-tracking code to ensure every n to n+1 upgrade sequence is accounted for. This Skill detects missing migration steps and validates that all schema and option shape changes between versions are correctly mapped.

How does dbDelta apply schema migrations during a plugin upgrade?ā–¼

dbDelta applies schema migrations during a plugin upgrade by validating that schema changes are correctly implemented in your version-tracking code. This Skill analyzes your migration logic to ensure dbDelta executes properly and maintains data integrity across version updates.

Why does my plugin need a version-tracking option for data migrations?ā–¼

A version-tracking option is needed for data migrations because it provides the baseline to determine which migration scripts must run. This Skill checks for the existence of a version-tracking option in your plugin to validate that data migrations are properly ordered and executed.

Can I use this Skill to detect option shape changes between plugin versions?ā–¼

Yes, you can use this Skill to detect option shape changes between plugin versions. It identifies plugins that modify their schema or option shape during upgrades and validates that the corresponding data migrations are performed correctly to prevent data corruption.

What happens if migration logic is not ordered correctly during a version upgrade?ā–¼

If migration logic is not ordered correctly during a version upgrade, data corruption can occur due to incomplete or overlapping schema changes. This Skill validates that data migrations are ordered and idempotent, ensuring data integrity is protected across all n to n+1 upgrade paths.