port-codebaseslisted

Plan, execute, review, and verify behavior-preserving codebase ports across programming languages, runtimes, frameworks, platforms, storage engines, or major APIs. Use when asked to rewrite or migrate an implementation while preserving semantics, mechanically translate a large body of code, replace a runtime or language, run a strangler or big-bang port, turn compiler and test failures into a migration queue, or organize AI-assisted porting with one or many agents. Scale the workflow to the available time, compute, and model budget without weakening correctness gates. Do not use for ordinary dependency bumps, small local refactors, or product redesigns disguised as a port.
sebastian-software/skills.sebastian-software.com · ★ 0 · AI & Automation · score 70

Install: claude install-skill sebastian-software/skills.sebastian-software.com

# Port Codebases Treat a port as a controlled behavior migration. Preserve observable contracts first; improve architecture and idioms after parity unless the user explicitly accepts combined migration risk. ## Establish Authority and Feasibility 1. Determine whether the user asked for assessment, a plan, a pilot, or the complete port. Do not turn analysis into a rewrite without authorization. 2. Inspect repository instructions, dirty state, build graph, supported platforms, tests, benchmarks, public APIs, foreign-function boundaries, generated code, and release constraints. 3. Compare porting with credible alternatives: targeted hardening, adapters, incremental replacement, or retaining the current implementation. State the failure class or strategic benefit that justifies the port. 4. Identify the equivalence oracle. Prefer a language-independent test suite, protocol fixtures, golden files, compatibility corpus, differential tests, or production traces. If no trustworthy oracle exists, build a bounded one before scaling implementation. 5. Read [Migration contract](references/migration-contract.md) and record the preserved behavior, allowed differences, exclusions, invariants, and gates. Stop and request direction when the source behavior is disputed, the target changes product semantics, or no affordable verification can distinguish a correct port from plausible-looking code. ## Choose a Resource Profile Read [Execution profiles](references/