rust-port-parity

Verify behavioral parity between a Rust port and its source via differential testing.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/FlexNetOS/envctl --skill rust-port-parity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-port-parity
Source: https://github.com/FlexNetOS/envctl/tree/main/.agents/skills/rust-port-parity
Command: npx skills add https://github.com/FlexNetOS/envctl --skill rust-port-parity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the verification of behavioral parity between a Rust port and its source code, ensuring that the port behaves identically under the same inputs.

Core Features & Use Cases

  • Differential Testing: Compares the behavior of a Rust port against its source code using the same inputs.
  • Golden Fixtures: Captures and compares the outputs, side effects, and error behavior.
  • Verification: Determines if the Rust port is faithful to the source, without downgrades.
  • Use Case: Before finalizing a Rust port, use this Skill to ensure it behaves as expected and does not introduce regressions.

Quick Start

Run the command 'rust-port-parity-verifier verify parity' to compare the Rust port with the source code.

Frequently Asked Questions about rust-port-parity

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

FAQPage Schema
How do I verify behavioral parity between a Rust port and its source code?

You verify behavioral parity by using differential testing to run both the Rust port and source code over identical inputs, then compare outputs and side effects for regressions.

What is differential testing for Rust code parity?

Differential testing for Rust code parity compares the behavior of a Rust port against its original source by feeding the same inputs to both and checking for matching outputs and side effects.

How do I check a Rust port for behavioral regressions before finalizing?

Check for behavioral regressions by capturing golden fixtures from the source and Rust port, then comparing their outputs and error behavior under identical test inputs.

Can I use golden fixtures to compare side effects in a Rust port?

Yes, golden fixtures capture and compare outputs, side effects, and error behavior to ensure the Rust port behaves identically to the source without downgrades.

What's the best way to ensure a Rust port does not introduce downgrades?

The best way to prevent downgrades is running automated differential testing that validates matching behavior and side effects between the Rust port and its original source code.