cheat-migrate

Upgrades Cheat state files to the latest schema via a defined migration chain.

12|Updated May 29, 2026
One-click install
npx skills add https://github.com/Jason5330/ai-self-eval --skill cheat-migrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cheat-migrate
Source: https://github.com/Jason5330/ai-self-eval/tree/main/skills/cheat-migrate
Command: npx skills add https://github.com/Jason5330/ai-self-eval --skill cheat-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrading old cheat-state.json files to the current schema_version by applying a defined, ordered migration chain derived from migrations/registry.md. The process is idempotent and will not advance if already up to date, ensuring safe re-runs.

Core Features & Use Cases

  • Deterministic migration steps executed in order to produce a consistent state across versions.
  • Backup-before-write semantics and failure-stopping behavior to preserve state integrity.
  • Registry-driven upgrade path with per-step migration files, enabling traceable and reversible changes when needed.
  • Use Case: You have a state file created by an older cheat version and need to upgrade it to the latest schema for compatibility with current skills.

Quick Start

Run cheat-migrate to upgrade your state from an old schema to the latest version.

Frequently Asked Questions about cheat-migrate

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

FAQPage Schema
How do I upgrade an old state file schema to the latest version?

To upgrade an old state file schema, apply a defined chain of migrations derived from a registry file to advance your state file to the latest schema_version.

Can I preview schema migration changes before applying them?

Yes, you can preview schema migration changes using a dry-run before executing the ordered migration chain to ensure the upgrade path is correct.

Is the state migration process idempotent and safe to run multiple times?

The state migration process is idempotent and will not advance if the schema is already up to date, ensuring safe re-runs without state corruption.

What files are required to execute the state file migration chain?

Executing the migration chain requires a root state file, a migrations registry file to determine the upgrade path, and per-step migration files under the migrations directory.

Does the migration tool create backups before writing the new schema?

The migration tool uses backup-before-write semantics and stops on failure, preserving state integrity while applying deterministic migration steps in order.