claude-skills-sync-migration

To migrate Claude skills, run the bootstrap-sync-skills.mjs script from the source repository to copy .agents/skills into the target project's .claude/skills path. This automated process generates sync scripts and injects package.json hooks for reliable setup.

The safest skill-sync workflow migration uses an atomic directory-switch strategy to prevent partial updates. This process includes runtime checks, idempotent updates, and rollback capabilities to ensure a reliable migration without corrupting existing project files.

Package.json postinstall hooks automatically trigger Claude skill-sync scripts during dependency installation. The migration process injects these hooks while ensuring an is-ci guard exists, preventing sync execution in inappropriate CI environments.

Atomic directory switching supports idempotent Claude skills updates by replacing the entire target directory only after verification passes. If runtime checks fail, the migration automatically rolls back, leaving the original .claude/skills path untouched.

Claude skills migrations fail in CI without an is-ci guard because postinstall hooks attempt to execute sync scripts during automated builds. The migration process injects this guard to ensure hooks only run locally, preventing unintended side effects in pipelines.

Migrating Claude skill-sync workflows applies idempotent updates, meaning it safely overwrites or regenerates sync scripts without duplicating entries. The atomic switch strategy ensures existing target files remain intact until the new migration is fully verified.