rewrite-rust-oneshot

Rewrite existing software projects into Rust while preserving behavior and passing quality gates.

1|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/PiercingXX/xx-stack --skill rewrite-rust-oneshot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rewrite-rust-oneshot
Source: https://github.com/PiercingXX/xx-stack/tree/main/runtime/skills/rewrite-rust-oneshot
Command: npx skills add https://github.com/PiercingXX/xx-stack --skill rewrite-rust-oneshot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It replaces a slow, failure-prone migration from an existing application to Rust by running an end-to-end one-shot rewrite and repeatedly fixing issues until the project’s quality gates pass.

Core Features & Use Cases

  • Non-stop migration loop: inventory, rewrite, and automatically iterate on compile and test failures until gates are green.
  • Behavior-preserving Rust rewrite: preserve user-visible behavior, API contracts, data formats, configuration semantics, and error/logging intent.
  • Production-oriented Rust standards: prioritize strong typing, explicit error handling, deterministic builds, and reproducible tests.

Quick Start

Ask the AI to run a nonstop rewrite of your current application into Rust while automatically fixing build and test failures until formatting, clippy, unit/integration tests, and release smoke checks are all passing.

Frequently Asked Questions about rewrite-rust-oneshot

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

FAQPage Schema
How do I automate a migration to Rust and ensure tests pass?

Automating a migration to Rust involves running a non-stop rewrite loop that scaffolds a workspace, ports tests, and iterates through failures until fmt, clippy, cargo test suites, release build, and release smoke checks all pass.

What is a one-shot Rust rewrite and how does it preserve existing behavior?

A one-shot Rust rewrite is an end-to-end migration that replaces an existing application while preserving user-visible behavior, API contracts, data formats, configuration semantics, and error/logging intent throughout the process.

Can I use an automated rewrite loop to port my tests to a Rust workspace?

Yes, an automated rewrite loop can scaffold a Rust workspace and port or recreate your existing tests, then repeatedly fix compile and test failures until all quality gates are green.

What quality gates must pass before a Rust migration is considered complete?

A Rust migration is only complete after fmt, clippy, cargo test suites, release build, and release smoke checks all pass, ensuring deterministic builds and reproducible tests.

Does an automated Rust rewrite support production-oriented standards like strong typing and explicit error handling?

Yes, an automated Rust rewrite prioritizes production-oriented standards including strong typing, explicit error handling, deterministic builds, and reproducible tests throughout the migration loop.

What are the limitations of an automated one-shot Rust rewrite?

An automated one-shot Rust rewrite requires deterministic build expectations and a non-stop loop, meaning it may struggle with non-deterministic environments or projects lacking clear behavioral contracts and test suites.