gen-rust

Sync Rust implementations with Python changes across core modules and tests.

11.1k|1.3k|Updated Oct 15, 2025
One-click install
npx skills add https://github.com/MoonshotAI/kimi-cli --skill gen-rust-moonshotai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gen-rust
Source: https://github.com/MoonshotAI/kimi-cli/tree/main/.agents/skills/gen-rust
Command: npx skills add https://github.com/MoonshotAI/kimi-cli --skill gen-rust-moonshotai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync Rust implementations with Python changes to keep behavior aligned between languages while excluding UI and login features.

Core Features & Use Cases

  • Mirror Python changes in Rust across core modules and utilities.
  • Align Rust tests with Python changes to maintain parity.
  • Document mappings, porting rules, and validation steps for future changes.

Quick Start

Port Python changes to Rust to maintain parity across core logic and 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 implementations with Python changes to maintain parity?

To sync Rust with Python changes, map Python sources to Rust targets across core modules, utilities, and tests. This ensures behavioral parity while excluding UI and login features from the synchronization workflow.

What is the best way to port Python logic to Rust without breaking existing tests?

Porting Python to Rust requires aligning Rust tests with Python changes to maintain parity. Document mappings, porting rules, and validation steps to ensure test synchronization and functional consistency across modules.

Does this Python to Rust synchronization workflow cover UI and login modules?

No, this Rust synchronization workflow explicitly excludes UI and login features. It focuses solely on keeping core logic, utilities, and test behaviors aligned between Python and Rust implementations.

How do I document mappings when porting Python code to Rust targets?

Document Python to Rust mappings by defining porting rules and validation steps for future changes. This maintains functional parity and establishes clear workflow expectations for code and test synchronization across modules.

Can I use this to align Rust tests with Python changes across build workflows?

Yes, this workflow aligns Rust tests with Python changes across build and test workflows. It ensures behavioral parity by mapping Python source modifications to corresponding Rust target validations.

When do I need to sync Rust code with Python modifications?

You need to sync Rust with Python when maintaining behavioral parity across cross-language implementations. This applies to code and test synchronization tasks across modules, mappings, and build workflows to ensure aligned functionality.