artifact-upgrade

Plan schema and artifact migrations with compatibility checks, backups, and rollback routes.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill artifact-upgrade-quydu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: artifact-upgrade
Source: https://github.com/QuyDu/Skills-Orchestrator/tree/main/.github/skills/artifact-upgrade
Command: npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill artifact-upgrade-quydu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Upgrading a schema or versioned artifact without breaking downstream consumers is risky: compatibility gaps, missing backups, and absent rollback paths can turn a routine version change into an incident. This Skill produces a governed migration plan with deterministic validation gates before any cutover happens. ## Core Features & Use Cases - Migration Planning: Defines phased migration steps covering preflight checks, backup or snapshot, forward change, verification, and rollback triggers. - Compatibility Matrix: Maps producer/consumer version combinations using dependency evidence from the skill dependency graph to identify required phased rollouts. - Rollback-First Safety: Produces rollback plans with objective triggers, restore order, and post-rollback validation, and fails closed when evidence is missing. - Use Case: When a report schema version changes and existing records must migrate, use this Skill to generate reports/artifact-upgrade-plan.json and reports/artifact-upgrade-report.md with forward and rollback sequences before touching any versioned artifact. ## Quick Start Ask the agent to plan a migration for the target schema or artifact, including a compatibility matrix, backup requirements, and a rollback plan with validation gates.

Frequently Asked Questions about artifact-upgrade

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

FAQPage Schema
How do I plan a schema migration without breaking downstream consumers?

Build a compatibility matrix of producer and consumer version combinations, then define phased migration steps with preflight checks, backups, verification, and rollback triggers. This Skill generates that plan as structured JSON and Markdown reports.

What should a database or schema rollback plan include?

A rollback plan needs objective rollback triggers, an explicit restore order, and post-rollback validation steps. Backup or snapshot requirements must be testable before cutover, and blocked prerequisites must be listed rather than marked successful.

When should I use artifact-upgrade instead of dependency-maintenance?

Use artifact-upgrade when a schema or artifact version changes and existing records must migrate. Use dependency-maintenance for application package upgrades, which follow a different workflow and ownership boundary.

Can a migration proceed without a validated rollback path?

No. The Skill fails closed when ownership, dependency evidence, or rollback viability is missing, and it never permits a cutover-ready conclusion without both forward and rollback validation paths.

Does planning a migration require approval before execution?

Yes. Explicit approval is required before executing any migration that mutates versioned artifacts, schemas, or consumer contracts. The Skill only writes its owned planning reports and never silently mutates source systems.