gen-rust

Name: gen-rust
Availability: InStock
Author: haomingz

Port Python module logic to Rust and update tests for parity.

12|2|Updated Apr 21, 2026

Search Tags:#python #rust #sync #tests #parity #porting #module-mapping

Ready to run

npx skills add https://github.com/haomingz/kimi-skills --skill gen-rust-haomingz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gen-rust
Source: https://github.com/haomingz/kimi-skills/tree/main/skills/gen-rust
Command: npx skills add https://github.com/haomingz/kimi-skills --skill gen-rust-haomingz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync Rust implementation with Python changes (excluding UI/login) by reviewing recent changes, mapping modules, porting logic, and updating tests to maintain functional parity between kagent runtimes.

Core Features & Use Cases

Review and align Rust code with the latest Python changes to keep behavior in sync.
Map Python modules to Rust equivalents, port logic, and refresh associated tests.
Use this workflow when preparing cross-language builds or validating parity between Python and Rust tooling.

Quick Start

Run the Rust sync workflow to compare Python changes with Rust, map modules, port logic, and update tests.

Frequently Asked Questions about gen-rust

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

FAQPage Schema

How do I sync Rust code with recent Python changes?▼

To sync Rust with Python changes, map Python modules to Rust equivalents, port the logic, and update tests to maintain functional parity. This workflow reviews recent changes and applies the mapping plan across modules while preserving error messages and outputs.

What is the best way to port Python logic to Rust while keeping tests in sync?▼

Porting Python logic to Rust involves mapping modules, porting the functional logic, and refreshing associated tests. You validate the ported logic by running existing Rust tests and E2E checks to ensure feature parity between the runtimes.

Does the Python to Rust module mapping workflow cover UI and login changes?▼

No, the Python to Rust module mapping workflow explicitly excludes UI and login-related changes. It focuses on porting core logic and tests to maintain functional parity for tooling and cross-language builds.

How do I validate feature parity after porting Python logic to Rust?▼

You validate feature parity after porting Python logic to Rust by running existing Rust tests and E2E checks. This ensures the behavior remains in lockstep and conforms to required mappings while preserving error messages and outputs.

When do I need to use a cross-language sync workflow for Python and Rust?▼

You need a cross-language sync workflow when preparing cross-language builds or validating parity between Python and Rust tooling. It is used to align Rust implementations with recent Python changes to keep kagent runtimes in lockstep.