gen-rust

Synchronize Rust implementations with Python changes across modules, tests, and tooling.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync Rust implementations with Python changes by reviewing recent changes, mapping modules, porting logic, and updating tests to keep parity, excluding UI and login/auth.

Core Features & Use Cases

  • Review and correlate Python changes with Rust counterparts to avoid drift.
  • Map modules and port logic accurately between languages, updating tests to reflect behavior.
  • Ensure parity in tooling and build expectations for the kagent/kosong/kaos stack.

Quick Start

Run the synchronization workflow after Python changes to align Rust code, tests, and tooling.

Frequently Asked Questions about gen-rust

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

FAQPage Schema
How do I keep Rust and Python implementations in sync after code changes?

To keep Rust and Python implementations in sync, review recent Python changes, map modules, port logic deterministically, and update tests to maintain parity. This excludes UI and login components.

How does deterministic porting from Python to Rust work?

Deterministic porting from Python to Rust works by enforcing an exact mapping of modules between the languages. It preserves error messages and updates tests to accurately reflect the original behavior.

Can I use code synchronization to align Rust tests with Python behavior changes?

Yes, code synchronization aligns Rust tests with Python behavior changes. The process maps modules, ports the updated logic, and updates the Rust test suite to reflect the new expected behavior.

Does Rust and Python code parity apply to UI and login components?

Rust and Python code parity does not apply to UI and login components. The synchronization process specifically excludes UI and login/auth modules to focus on core logic, tooling, and tests.

What is the best way to prevent drift between Python and Rust codebases?

The best way to prevent drift is to correlate Python changes with Rust counterparts and run a synchronization workflow. This enforces exact module mapping, preserves error messages, and updates tests.