cross-repo-health

Verify build and test health of meta workspace repositories with cargo checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Ensures a consistent, green build/test/lint baseline across all meta workspace repositories, enabling continuous integration and reliable development cycles.

Core Features & Use Cases

  • Green Build Baseline: Establishes a baseline of green builds for each repository, triggering health checks upon every integration.
  • Rust-native Implementation: Utilizes Rust's cargo tooling for compile, build, lint, and test checks.
  • Quick Start: Execute the cross-repo-health skill to validate the health of all repositories.

Quick Start

Run the cross-repo-health skill to ensure all meta workspace repositories are green.

Frequently Asked Questions about cross-repo-health

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

FAQPage Schema
How do I ensure consistent build health across multiple Rust workspace repositories?

To ensure consistent build health across multiple Rust repositories, you can run automated checks like cargo build, cargo check, and cargo clippy. This skill establishes a green build baseline for meta workspace repos, triggering validations upon every integration.

How do I run cargo clippy and cargo check in a CI/CD pipeline for meta workspace repos?

To run cargo clippy and cargo check in a CI/CD pipeline for meta workspace repos, execute the cross-repo-health skill. It utilizes native Rust cargo tooling to automatically perform compile, build, lint, and test checks across all configured repositories.

What is a green build baseline and when do I need it for Rust repository health?

A green build baseline is a verified state where all compile, test, and lint checks pass successfully. You need it for Rust repository health to enable continuous integration and maintain reliable development cycles across meta workspace repositories.

Can I use this skill to verify repository dependencies and configurations for Rust projects?

Yes, you can use this skill to verify repository dependencies and configurations for Rust projects. It ensures the integrity of meta workspace repositories by executing Rust-based health checks during CI/CD pipelines and integration workflows.

What is the best way to automate Rust code quality and lint checks across multiple repositories?

The best way to automate Rust code quality and lint checks across multiple repositories is to establish a continuous integration baseline. This skill executes cargo clippy and build checks across meta workspace repos, validating health and integrity upon every integration.