gen-rust

Synchronize Python changes with Rust implementations using explicit module mappings.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronize Python changes with Rust implementations to maintain parity between the Python and Rust versions while excluding UI and login.

Core Features & Use Cases

  • Align core logic and behavior across Python and Rust by mirroring changes in modules, utilities, and tests.
  • Map Python code locations to Rust equivalents to ensure feature parity and consistent test outcomes.
  • Support end-to-end parity checks and update workflows when Python changes are introduced in the repo.

Quick Start

Review recent Python changes and mirror them in Rust using the mapping guidelines.

Frequently Asked Questions about gen-rust

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

FAQPage Schema
How do I synchronize Python changes with a Rust codebase?

To synchronize Python changes with a Rust codebase, you map the updated Python modules to their Rust equivalents and mirror the logic changes, ensuring error messages and test outcomes remain consistent.

What is the best way to maintain feature parity between Python and Rust ports?

Maintaining feature parity between Python and Rust ports requires explicit Python-to-Rust module mappings and coordinated end-to-end parity checks whenever Python changes are introduced in the repository.

Does porting Python logic to Rust require updating E2E tests?

Yes, porting Python logic to Rust requires updating E2E tests, as the synchronization process coordinates both unit and end-to-end parity workflows to verify consistent behavior across both versions.

What should I exclude when mirroring Python changes in Rust implementations?

When mirroring Python changes in Rust implementations, you should exclude UI and authentication logic, focusing strictly on core logic, module mappings, and test updates.

Why do my Rust porting workflows require explicit Python-to-Rust mappings?

Rust porting workflows require explicit Python-to-Rust mappings to accurately locate the corresponding code locations, ensuring feature parity and consistent test outcomes without guessing the target structure.

Can I preserve original Python error messages when updating Rust code?

Yes, you can and should preserve original Python error messages and outputs when updating the Rust codebase to maintain behavioral parity across both implementations.