rust-port-inventory

Create a parity ledger of source project components for Rust porting.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive inventory of a source project for a Rust port, building a parity ledger that ensures nothing is overlooked during the porting process.

Core Features & Use Cases

  • Parity Ledger Creation: Builds a parity ledger of every module, export, behavior, error path, config, CLI, route, side effect, and edge case in the source project.
  • Source Inventory: Exhaustively lists all relevant aspects of the source project, including config keys, CLI flags, HTTP routes, background jobs, and serialization formats.
  • Use Case: Before starting a Rust port, use this Skill to ensure that all necessary components and behaviors are accounted for and to maintain a comprehensive list for reference.

Quick Start

Use the rust-port-inventory skill to inventory the source project 'source-project'.

Frequently Asked Questions about rust-port-inventory

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

FAQPage Schema
How do I create a parity ledger before porting a project to Rust?

To create a parity ledger for a Rust port, you need to analyze the source project files, configuration, and behavior to output a comprehensive list of components and their details.

What is a Rust port inventory and when do I need one?

A Rust port inventory is an exhaustive list of source project aspects like config keys, CLI flags, HTTP routes, and side effects. You need one before starting a port to ensure no components are overlooked.

How do I inventory all source project behaviors for a Rust port?

You inventory source project behaviors by analyzing the source project files using AST and symbol analysis tooling, which outputs a comprehensive ledger of modules, exports, error paths, and edge cases.

Does building a port parity ledger require special tooling?

Yes, building a port parity ledger requires source project files and relevant tooling for AST and symbol analysis to exhaustively capture all modules, config keys, and serialization formats.

Can I track CLI flags and HTTP routes when porting to Rust?

Yes, you can track CLI flags and HTTP routes by running a source inventory that exhaustively lists all relevant aspects of the source project, including background jobs and serialization formats.

What's the best way to ensure completeness in a Rust porting effort?

The best way to ensure completeness in a Rust porting effort is to generate a parity ledger that accounts for every module, export, behavior, config, route, and edge case in the source project.