{"enrichment":{"faq":[{"a":"rust-quality-gate is a three-stage quality protocol for Rust code that runs format validation, clippy linting, and test execution in sequence, halting on any failure. Use it before merging code or when your changes are ready to commit. It's designed for the trusty-tools monorepo and ensures code meets formatting standards, passes linting checks, and has no broken tests.","q":"What is rust-quality-gate and when should I use it?"},{"a":"rust-quality-gate enforces a strict three-gate sequence: first cargo fmt to validate formatting, then clippy for linting warnings, then cargo test for the full workspace test suite. Each stage halts on failure, preventing later stages from running. This ensures code quality gates are applied consistently before any merge.","q":"How do I run cargo fmt clippy test in the right sequence?"},{"a":"rust-quality-gate verifies your code is merge-ready by running all three quality checks: format compliance, clippy linting, and workspace-wide tests. If all stages pass without halting, your code meets the quality standards. The protocol also clarifies crate naming conventions and helps distinguish pre-existing test failures from new ones introduced by your changes.","q":"Is my Rust code ready to merge with rust-quality-gate?"},{"a":"rust-quality-gate executes workspace-wide tests with proper crate scoping, which validates that changes to shared libraries don't break dependent crates. By running the full test suite across all crates in the trusty-tools monorepo, it catches integration issues that single-crate testing might miss.","q":"How does rust-quality-gate validate shared library changes?"},{"a":"rust-quality-gate provides guidance on triaging and distinguishing pre-existing test failures from new ones introduced by your code changes. This helps you identify whether a failure is caused by your modification or was already present, making it easier to focus on actual regressions during code review.","q":"Can rust-quality-gate distinguish pre-existing test failures?"}],"shadow_tags":["pre-merge-validation","code-quality-automation","rust-toolchain-integration","ci-cd-protocol","static-analysis-workflow","test-automation-framework","monorepo-governance","lint-enforcement","workspace-testing"],"summary_rewrite":"This protocol enforces a three-stage quality check for Rust code: format validation, clippy linting, and test execution, each halting on failure. It's designed for the trusty-tools monorepo and clarifies crate naming conventions, test output interpretation, and handling of pre-existing failures. Use it before any PR merge or when code changes are ready to commit."},"files":[{"bytes":6930,"path":"toolchains/rust/quality/rust-quality-gate/SKILL.md","sha256":"348f3f8b20d5fb3869e2d0c7bab60d92269d2c871e8ace537659d5f289dbe1af","url":"https://skillfed.io/files/bobmatnyc/claude-mpm-skills/rust-quality-gate/3fc369e2/SKILL.md"}],"id":"bobmatnyc/claude-mpm-skills/rust-quality-gate","links":{"html":"https://skillfed.io/bobmatnyc/claude-mpm-skills/rust-quality-gate","md":"https://skillfed.io/bobmatnyc/claude-mpm-skills/rust-quality-gate.md","repo":"https://github.com/bobmatnyc/claude-mpm-skills"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":18,"language":"Python","last_updated":"2026-07-18","license":"MIT","name":"rust-quality-gate","publisher":"bobmatnyc","stars":62},"relations":{"similar":[{"id":"bobmatnyc/claude-mpm-skills/cargo-release"},{"id":"bobmatnyc/claude-mpm-skills/ort"},{"id":"moonrepo/moon/improve-code-quality"},{"id":"existential-birds/beagle/rust-project-setup"},{"id":"warpdotdev/common-skills/fix-errors"},{"id":"mosif16/codex-Skills/Rust"},{"id":"existential-birds/beagle/rust-best-practices"},{"id":"CuriousLearner/devkit/rust-cargo-assistant"},{"id":"coralogix/cx-cli/run-tests"},{"id":"rtk-ai/rtk/ship"}]},"slug":{"owner":"bobmatnyc","repo":"claude-mpm-skills","skill":"rust-quality-gate"},"version":"3fc369e2"}