rust-quality-gate
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.
rust-quality-gate runs format, lint, and test checks in sequence to validate Rust code before merging.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-18
rust-quality-gate runs format, lint, and test checks in sequence to validate Rust code before merging. 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.
Use it when
- rust-quality-gate enforces a strict three-gate sequence: first cargo fmt to validate formatting, then clippy for linting warnings.
- rust-quality-gate verifies your code is merge-ready by running all three quality checks: format compliance, clippy linting.
Verify before relying
Read SKILL.md below before installing (2 files). Open directory: indexed for reading, not audited.
Similar skills
Install
bobmatnyc/claude-mpm-skills/rust-quality-gate · repository language: Python
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What is rust-quality-gate and when should I use it?
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.
How do I run cargo fmt clippy test in the right sequence?
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.
Is my Rust code ready to merge with rust-quality-gate?
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.
How does rust-quality-gate validate shared library changes?
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.
Can rust-quality-gate distinguish pre-existing test failures?
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.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Rust Quality Gate Protocol
When to Invoke
Invoke this protocol when: - Any implementation task completes and code changes are ready to commit - User asks "check quality", "run tests", "run clippy", "is this ready", or
(truncated - see the full file via the links below)
File tree — 2 files
toolchains/rust/quality/rust-quality-gate/SKILL.md
toolchains/rust/quality/rust-quality-gate/metadata.json
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Run Rust quality gates (fmt, clippy, test) before merging code”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
This skill automates the complete Cargo release workflow for Rust monorepos, enforcing a 10-step sequence that includes semver versioning, dependency updates, test and lint gates, git tagging, and crates.io publishing. It handles cross-crate dependency ordering, workspace version management for the trusty-mpm family, and includes critical macOS codesign safety rules to prevent signing cache crashes.
Ship orchestrates the full release cycle for RTK projects: quality verification, semantic versioning, changelog generation, git tagging, and remote push to activate CI/CD pipelines. Follow pre-release checklists, execute the multi-step workflow, and verify post-release artifacts automatically.
This skill automates Definition of Done enforcement by detecting your project type and running all quality gates—type checking, linting, dead code detection, and tests—in sequence. It captures failures by category, provides specific fixes, and re-runs gates until everything passes, ensuring code truly meets your standards before task completion.
This guide explores Swift's native concurrency model, contrasting it with legacy Grand Central Dispatch approaches. You'll examine the cooperative thread pool, async/await state machines, structured concurrency hierarchies, and the Actor model's data safety guarantees. The material covers Swift 6 strict concurrency requirements, migration tactics, and synchronization primitives for building robust applications.
RFC Writer guides you through composing normative RFCs—product contracts with observable obligations, invariants, and compatibility rules. It enforces separation between specification prose and implementation details, ensures each clause is independently testable, and hands off lifecycle operations to dedicated governance tools. Use it to author the contract itself, not design rationale or execution scope.
gws-shared is a reference guide for the gws CLI's core patterns: browser-based OAuth and service account authentication, global flags for output formatting and API validation, and method-specific options for pagination and file handling. It covers essential syntax, shell quoting tips, and security practices for working with Google Workspace APIs.
More skills mypy (MIT)