migrating-to-product-sdk

Detect legacy product codebases and write migration specs for @parity/product-sdk.

8|3|Updated Mar 31, 2026

Search Tags:#codebase #migration #software migration #automated migration #product-sdk

Ready to run

npx skills add https://github.com/paritytech/product-sdk --skill migrating-to-product-sdk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migrating-to-product-sdk
Source: https://github.com/paritytech/product-sdk/tree/main/product-sdk/skills/migrating-to-product-sdk
Command: npx skills add https://github.com/paritytech/product-sdk --skill migrating-to-product-sdk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the migration of product codebases to the @parity/product-sdk, detecting legacy stacks and creating migration specifications without editing code or running tests.

Core Features & Use Cases

Detection of Legacy Stacks: Identifies legacy stacks like polkadot-apps, novasamatech, hand-rolled crypto/IPFS, and polkadot-api 1.x in the target repo.
Decision Matrix: Determines which migration areas apply, creating a migration spec with user approval.
Spec Writing: Outputs a migration spec at .claude/migrations/specs/, and can be committed or opened as a GitHub issue.

Quick Start

Migrate a product codebase to @parity/product-sdk using the migrating-to-product-sdk skill.

Frequently Asked Questions about migrating-to-product-sdk

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

FAQPage Schema

How do I automate codebase migration to @parity/product-sdk?▼

Automating codebase migration to @parity/product-sdk requires this Skill to detect legacy stacks and generate a migration spec. It creates a decision matrix and writes specifications to `.claude/migrations/specs/` without modifying code or running tests.

What legacy stacks are detected during product-sdk migration?▼

Legacy stacks detected during product-sdk migration include polkadot-apps, novasamatech, hand-rolled crypto/IPFS, and polkadot-api 1.x. The Skill identifies these stacks in the target repo and determines which migration areas apply using a decision matrix.

How do I generate a migration spec for a legacy product codebase?▼

Generating a migration spec for a legacy product codebase involves running the Skill against a target workspace containing package.json files. It outputs the specification at `.claude/migrations/specs/`, which can be committed or opened as a GitHub issue.

Can I use automated migration to modify code and run tests automatically?▼

Automated migration to product-sdk cannot be used to modify code or run tests. The Skill performs discovery, decision matrix analysis, and spec writing, requiring human approval at checkpoints before any downstream code changes are made.

Do I need package.json files to migrate a codebase to product-sdk?▼

Package.json files are required to migrate a codebase to product-sdk. The Skill needs a target workspace with package.json files and potential dependencies to perform discovery and generate the migration specification accurately.

Why does product-sdk migration require human approval at checkpoints?▼

Product-sdk migration requires human approval at checkpoints because the Skill only generates specifications and does not modify code. This ensures developers review the decision matrix analysis and migration spec before proceeding with actual code changes.