inno-migrate-app

Migrates an existing repository onto the Innovation Platform by registering it in place and adapting it to the platform contract.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/dlaporte/claude-plugins --skill inno-migrate-app-dlaporte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inno-migrate-app
Source: https://github.com/dlaporte/claude-plugins/tree/main/plugins/innovation-platform/skills/inno-migrate-app
Command: npx skills add https://github.com/dlaporte/claude-plugins --skill inno-migrate-app-dlaporte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Moving an existing codebase onto the davidlaporte.org Innovation Platform requires satisfying a strict deployment contract (port 8080, /healthz, app/ layout, gateway-based identity) and passing security gates; this Skill assesses the repo, plans the migration, and adapts the code in place without copying it into a new repository. ## Core Features & Use Cases - Read-only migration assessment: Evaluates stack compatibility, deployment type (container, function, mcp-function, mcp-container), auth to strip, persistence to port to D1/R2, and gate risks such as secrets in git history, CVEs, and forbidden paths. - In-place registration and adaptation: Registers the user's own repo via the register_app MCP tool with a proof-of-control file, installs the platform GitHub App, adds the deploy.yml caller workflow, and rewires the code to the platform contract. - Use Case: A user says "deploy this repo to the innovation platform"; the Skill scans the repo, presents a written migration plan for approval, then registers and adapts the repo so it passes CI gates and ships. ## Quick Start Ask the assistant to migrate your existing repository to the Innovation Platform, for example by saying "deploy this repo to the innovation platform".

Frequently Asked Questions about inno-migrate-app

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

FAQPage Schema
How do I deploy an existing repo to the Innovation Platform?

Run a migration assessment against the platform contract, get the written plan approved, then register the repo with register_app, commit the proof-of-control file, install the platform GitHub App, and adapt the code in place to listen on port 8080 with /healthz.

Does migrating to the Innovation Platform require rewriting my app's stack?

No. The platform contract is HTTP on port 8080 or a Cloudflare Worker fetch handler, not a specific language, so keeping the existing stack is the default. Rewrites are only considered when the user deliberately opts into a function deployment type.

What happens to my app's existing login and OAuth code during migration?

Front-door authentication is removed entirely because the gateway verifies users against Okta and injects X-Forwarded-User and X-Forwarded-Groups headers. Per-user backend auth to external services is replaced by a platform Connection rather than ported.

Why does migration fail on secrets in old git commits?

The secrets gate scans full git history with gitleaks, and since the same repo is migrated, a credential in any past commit still fails. The secret must be rotated, scrubbed from history, and stored as an app Variable instead.

What files are forbidden at the repo root on the Innovation Platform?

The config-integrity gate rejects a root src/ directory, root package.json, package-lock.json and tsconfig.json, root wrangler configs, any .npmrc at any depth, root .env files, scaffold/ directories, and committed symlinks resolving to directories.

Can I migrate an MCP server to the Innovation Platform?

Yes. A TypeScript MCP source maps to the mcp-function type and a Python source to mcp-container with a stateless POST /mcp endpoint. If the server needs a per-user Connection to a backend, it must use mcp-container regardless of language.