Migrate an internal package into Ghost

Migrate an internal package into Ghost

Move a package from another TryGhost repository into Ghost without losing its history or creating a period where neither repository owns it. Keep migration mechanics separate from Ghost's lifetime package standards.

Any contributor can run this skill. Do not require repository administration permission for the audit, import, PR preparation, CI, read-only preflight, post-merge verification or follow-up work. Administration is required only at the exceptional merge checkpoint, which is handed to one of the small set of Ghost repository administrators.

The contributor workflow is documented in docs/contributing/internal-package-migrations.md. Keep that guide aligned when this skill changes its outputs or human checkpoints.

Authority boundaries

Explain every cross-repository or administrative action before it happens.

• A request for instructions is not permission to perform the action.
• If the user says "tell me how, I do it", provide the command and wait.
• Require explicit authorization before changing repository settings, merging a PR, deprecating npm versions, or force-pushing.
• Never run the history import's --confirm operation. That command is the deliberate human administrator checkpoint because it temporarily changes a Ghost repository setting and merges the exceptional PR.
• Never ask for, display, or store credentials or OTPs.

Work in isolated checkouts

Never manipulate history in a checkout containing unrelated work. Fetch both repositories, confirm the source checkout is clean, and create a dedicated Ghost worktree from the freshly fetched origin/main.

Run history-changing commands individually or in a fail-fast shell. A failed git worktree add must not be followed by git subtree add in whichever checkout happens to be current. Before choosing a branch or path, list existing worktrees and matching local and remote branches. Use a migration-specific slug,