codemod-rust-workspace

Name: codemod-rust-workspace
Availability: InStock
Author: Codemod

Coordinate and validate Rust workspace crates for governance and CI parity.

1.1k|81|Updated Jan 26, 2024

Search Tags:#workflow #testing #workspace #rust #cargo #ci

Ready to run

npx skills add https://github.com/codemod/codemod --skill codemod-rust-workspace

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: codemod-rust-workspace
Source: https://github.com/codemod/codemod/tree/main/.agents/skills/codemod-rust-workspace
Command: npx skills add https://github.com/codemod/codemod --skill codemod-rust-workspace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate and validate Codemod's Rust workspace to ensure consistent crate governance, testing, and CI parity across the monorepo.

Core Features & Use Cases

Clarifies crate responsibilities (butterflow-models, butterflow-core, butterflow-state, butterflow-runners, butterflow-scheduler, codemod crates, testing-utils) to ensure consistent interfaces.
Enforces workspace dependencies and unified validation, including schema generation and cargo tasks.
Ensures code quality, including async cancellation, error propagation, and CI parity across crates.

Quick Start

Read the nearest AGENTS.md, identify the crate role, and apply the workspace governance rules.

Frequently Asked Questions about codemod-rust-workspace

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

FAQPage Schema

How do I enforce consistent crate governance and dependency rules in a Rust monorepo workspace?▼

To enforce crate governance in a Rust workspace, you coordinate crate responsibilities and validate workspace dependencies to ensure consistent interfaces, schema generation, and unified validation across all components.

What is the best way to maintain CI parity and code quality across multiple Rust crates?▼

Maintaining CI parity across Rust crates requires coordinating workspace validation to enforce code quality standards, including async cancellation, error propagation, and consistent cargo tasks across the monorepo.

How do I manage schema generation workflows and cargo tasks for state adapters and runners in Rust?▼

Managing schema generation and cargo tasks involves enforcing unified workspace validation rules that span state adapters, runners, and models, ensuring consistent interfaces and dependency propagation throughout the workspace.

Can I use workspace governance rules to clarify crate responsibilities for a Rust scheduler and CLI?▼

Yes, workspace governance rules clarify distinct crate responsibilities for components like the scheduler and CLI surfaces, ensuring they maintain consistent interfaces and appropriate dependency boundaries within the monorepo.

Why do I need to validate async cancellation and error propagation across my Rust workspace?▼

Validating async cancellation and error propagation is necessary to ensure code quality and runtime stability across independent crates, preventing silent failures and maintaining CI parity throughout the Rust workspace.