translate-programming-language

Plan and execute language-to-language migrations with behavior parity.

320|3|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/mizchi/skills --skill translate-programming-language
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: translate-programming-language
Source: https://github.com/mizchi/skills/tree/main/lang/translate-programming-language
Command: npx skills add https://github.com/mizchi/skills --skill translate-programming-language

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Plan and execute language-to-language server or application migrations with behavior parity. Use when porting modules, services, APIs, or runtimes between programming languages; generating source-runtime oracles and fixtures; generating migrated parity tests; detecting runtime, standard-library, serialization, numeric, encoding, time, regex, or protocol differences; building temporary compatibility layers; accumulating migration knowledge; benchmarking; shadow testing; canarying; or planning cutover and rollback.

Core Features & Use Cases

  • Oracle-driven parity workflow to plan and execute migrations.
  • Generate source-runtime fixtures and parity tests to validate behavior.
  • Build and maintain a compatibility knowledge base to guide cutover and rollback.
  • Rollout-and-cutover verification through drift checks, shadow/replay, and benchmarks.

Quick Start

Define the migration boundary and run the oracle-driven parity workflow to generate fixtures and tests.

Frequently Asked Questions about translate-programming-language

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

FAQPage Schema
How do I port application logic across programming languages while ensuring behavior parity?

To port application logic with behavior parity, define the migration boundary and run an oracle-driven workflow that generates source-runtime fixtures and parity tests to validate matching behavior across languages.

What is an oracle-driven parity workflow for server migration?

An oracle-driven parity workflow records standard behavior from your source language runtime to generate oracles and fixtures, which are then used to verify the migrated application and detect runtime or standard-library differences.

How do I detect serialization, encoding, or time differences during a cross-language migration?

Detect serialization, encoding, time, numeric, and regex differences by generating source-runtime oracles and fixtures that compare standard library outputs, exposing protocol and runtime drift during the migration process.

Can I use shadow testing and canarying to safely cutover a migrated service?

Yes, you can use shadow testing, replay, and benchmarking to verify rollout readiness, build a compatibility knowledge base, and execute a safe cutover with documented rollback guidance for the migrated service.

What are the limitations of relying on parity tests for API migration?

Parity tests detect runtime and standard-library drift but may not capture undocumented edge cases or performance bottlenecks, so you should benchmark and accumulate migration knowledge to supplement fixture-based testing during cutover.