gen-rust

Port Python changes to Rust with exact output and error parity.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/chen-001/kimi-cli-plus --skill gen-rust-chen-001
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gen-rust
Source: https://github.com/chen-001/kimi-cli-plus/tree/main/.agents/skills/gen-rust
Command: npx skills add https://github.com/chen-001/kimi-cli-plus --skill gen-rust-chen-001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures Rust implementation stays logically identical to Python changes by reviewing recent changes, mapping modules, porting logic, and updating tests, excluding UI and login/auth.

Core Features & Use Cases

  • Code parity: keeps Rust behavior and tests aligned with Python changes.
  • Module mapping: defines a clear Python-to-Rust file path mapping and workflow.
  • Guided porting: provides step-by-step workflow to port logic while preserving outputs and error messages.

Quick Start

Review recent Python changes and port them to Rust, updating tests and ensuring parity.

Frequently Asked Questions about gen-rust

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

FAQPage Schema
How do I keep a Rust port in parity with Python code changes?

To keep Rust in parity with Python code changes, review recent Python updates, map file paths between modules, port the logic, and update tests to ensure exact textual parity in outputs and error messages.

What is the workflow for porting Python logic to Rust?

The porting workflow involves reviewing Python changes, mapping Python-to-Rust file paths, porting the logic step-by-step, and comprehensively updating tests to maintain end-to-end behavioral parity.

Does Python-to-Rust porting require exact matching for error messages?

Yes, Python-to-Rust porting requires exact textual parity in error messages and outputs, ensuring the Rust implementation remains logically identical to the Python source behavior.

What is excluded when syncing Python changes to Rust?

When syncing Python changes to Rust, UI and login or authentication modules are explicitly excluded from the porting and parity workflow, focusing only on code modules, tests, and tooling.

Which directories are targeted when mapping Python to Rust?

Python to Rust mapping targets the src/kimi_cli and packages/kaos directories along with related Rust targets, applying changes to code modules, tests, and tooling.