From accelerator
Applies pending Accelerator meta-directory migrations to update repo to latest plugin schema. Guarded: refuses dirty tree, previews each migration before destructive writes.
npx claudepluginhub atomicinnovation/accelerator --plugin acceleratorThis skill is limited to using the following tools:
> **Warning: this skill rewrites files in `meta/` and `.claude/accelerator*.md`.** Recovery is via VCS revert. Before running, ensure your repo is committed and you understand what each pending migration does. The safety guards (clean-tree check, preview) exist to give you a moment to stop — they are not a substitute for understanding the changes.
migrations/0001-rename-tickets-to-work.shmigrations/0002-rename-work-items-with-project-prefix.shscripts/run-migrations.shscripts/test-fixtures/0002/meta/plans/2026-04-01-some-plan.mdscripts/test-fixtures/0002/meta/research/2026-04-02-research.mdscripts/test-fixtures/0002/meta/research/2026-04-03-history.mdscripts/test-fixtures/0002/meta/work/0001-add-foo.mdscripts/test-fixtures/0002/meta/work/0042-add-bar.mdscripts/test-fixtures/0002/meta/work/0099-bare-frontmatter.mdscripts/test-fixtures/0002/meta/work/notes.mdscripts/test-migrate.shMigrates npm-installed metaswarm (`npx metaswarm init`) to marketplace plugin: git-stages removal of redundant .claude/plugins/metaswarm/, rubrics, guides with safety checks. Reversible.
Plans and executes phased migrations for framework upgrades, API bumps, dependency major versions, and deprecations with compatibility verification.
Orchestrates full migration workflows from current state analysis through planning, incremental implementation, and verification for technologies, platforms, and architecture patterns with rollback planning.
Share bugs, ideas, or general feedback.
Warning: this skill rewrites files in
meta/and.claude/accelerator*.md. Recovery is via VCS revert. Before running, ensure your repo is committed and you understand what each pending migration does. The safety guards (clean-tree check, preview) exist to give you a moment to stop — they are not a substitute for understanding the changes.
Run /accelerator:migrate after upgrading the Accelerator plugin to a version that bundles new migrations. The SessionStart hook will tell you when this is needed:
[accelerator] meta/.migrations-applied is behind the plugin
(highest applied: 0001-rename-tickets-to-work; highest available: 0002-...).
Run /accelerator:migrate to bring it up to date.
You can also run it proactively — if no migrations are pending, it prints No pending migrations. and exits cleanly.
The driver script skills/config/migrate/scripts/run-migrations.sh orchestrates the migration lifecycle:
meta/ and .claude/accelerator*.md for uncommitted changes. Aborts if any are found. Set ACCELERATOR_MIGRATE_FORCE=1 to bypass (advanced users only).meta/.migrations-applied and meta/.migrations-skipped — newline-delimited lists of migration IDs. If either file is absent, its set is empty. Unknown IDs (from a newer plugin version) are preserved verbatim and warned about. An ID appearing in both files triggers a warning; applied takes precedence.skills/config/migrate/migrations/[0-9][0-9][0-9][0-9]-*.sh in sorted order. The directory can be overridden via ACCELERATOR_MIGRATIONS_DIR (used in tests).<ID> — <description> — with a per-migration skip hint (--skip <id>). If nothing is pending, prints No pending migrations. (plus any skipped names) and exits 0 immediately.PROJECT_ROOT exported; on success atomically appends its ID to meta/.migrations-applied; on failure prints the migration's output to stderr, exits 1, and leaves the state file at the last successful migration. If the migration emits MIGRATION_RESULT: no_op_pending on stdout, it is treated as a soft skip — the migration stays pending and will be retried on future runs.Each migration script under migrations/ must:
#!/usr/bin/env bash then # DESCRIPTION: <short imperative description> on line 2PROJECT_ROOT as an exported env var pointing to the consumer reposcripts/atomic-common.sh for atomic_write, atomic_append_unique, atomic_remove_line) for any file rewritesDRY_RUN env var — this framework has no dry-run modeMIGRATION_RESULT: no_op_pending on stdout to signal that preconditions are not met and the migration should remain pending (retried on future runs)meta/.migrations-applied contains one migration ID per line, in the order migrations were applied:
0001-rename-tickets-to-work
0002-some-future-migration
meta/.migrations-skipped contains one migration ID per line for migrations the user has chosen to defer:
0002-some-future-migration
Both files are human-readable and constitute the audit trail. Do not edit them manually unless you are deliberately marking a migration as applied, unapplied, or skipped.
Skip a migration to defer it indefinitely:
bash "${CLAUDE_PLUGIN_ROOT}/skills/config/migrate/scripts/run-migrations.sh" --skip <migration-id>
Unskip a previously skipped migration so it becomes pending again:
bash "${CLAUDE_PLUGIN_ROOT}/skills/config/migrate/scripts/run-migrations.sh" --unskip <migration-id>
Skipped migrations never run and do not block other pending migrations. The pre-run banner includes a --skip hint for each pending migration. ACCELERATOR_MIGRATE_FORCE=1 bypasses the dirty-tree pre-flight only; skipped migrations remain skipped even with FORCE.
A migration that exits 0 and emits MIGRATION_RESULT: no_op_pending on stdout is treated as a soft deferral — it stays pending and will be retried on future runs. The sentinel line is stripped from user-visible output.
Migrations emitting this sentinel MUST guarantee they performed no destructive operations before the line was emitted. Migrations doing destructive work must either succeed (recorded as applied) or fail non-zero.
Invoke via Bash:
bash "${CLAUDE_PLUGIN_ROOT}/skills/config/migrate/scripts/run-migrations.sh"
The driver script resolves PROJECT_ROOT automatically from the current working directory. Run it from within the consumer repository. Run /accelerator:migrate from a single shell at a time; it does not acquire a lock.
meta/decisions/ADR-0023-migration-framework.md — framework design rationaleskills/config/init/SKILL.md — init bootstraps fresh repos; migrate upgrades existing onesskills/config/configure/SKILL.md — configuration reference