lift-module

Port Python modules to TypeScript with parity testing and integration verification.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/ammonfife/sakima.co --skill lift-module
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lift-module
Source: https://github.com/ammonfife/sakima.co/tree/main/.claude/skills/lift-module
Command: npx skills add https://github.com/ammonfife/sakima.co --skill lift-module

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of porting Python modules to TypeScript, ensuring that the functionality is preserved and parity between the two languages is maintained.

Core Features & Use Cases

  • Python to TypeScript Porting: Converts Python modules to TypeScript with a focus on functionality and parity.
  • Parity Testing: Ensures that the TypeScript module produces identical results as the Python module.
  • Screenshot Proofing: Captures a screenshot of the TypeScript module in action to verify its correctness.
  • Use Case: For developers working on a consolidation project, this Skill can be used to port Python modules from auction_tools/ to lkup.info/shared/, ensuring seamless integration and accuracy.

Quick Start

To port a module named 'module-name', run: lift-module <module-name>

Frequently Asked Questions about lift-module

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

FAQPage Schema
How do I port Python modules to TypeScript while ensuring functional parity?

To port Python modules to TypeScript with functional parity, you need a process that analyzes source code, creates the TypeScript module, and runs parity testing to verify identical results. This ensures accuracy and compliance.

What is the best way to automate Python to TypeScript code conversion for a consolidation project?

Automating Python to TypeScript code conversion involves pre-flight checks, source code analysis, module creation, and integration verification. This workflow seamlessly ports Python modules into a shared TypeScript directory while maintaining functionality.

Do I need both Python and TypeScript environments to run module porting tasks?

Yes, module porting requires Python for source code access and TypeScript for porting. Both environments are necessary to analyze the original Python modules and generate accurate, compliant TypeScript replacements.

How does parity testing work when converting Python code to TypeScript?

Parity testing verifies that the newly created TypeScript module produces identical results to the original Python module. It is a core phase of the porting process that ensures accuracy and functional equivalence before integration.

Can I verify TypeScript module porting accuracy using screenshot proofing?

Yes, screenshot proofing captures the TypeScript module in action to visually verify its correctness. This step complements parity testing by confirming that the ported code behaves as expected in a live environment.

What are the limitations of automated code conversion from Python to TypeScript?

Automated code conversion requires pre-flight checks and source code analysis to handle language differences. Limitations arise if the Python source is inaccessible or if integration verification fails due to non-portable dependencies.