quality-gates

Name: quality-gates
Availability: InStock
Author: monktui

Define done criteria and verify Rust code with cargo test, clippy, and fmt.

Updated Feb 10, 2026

Search Tags:#linting #definition of done #pre-commit hooks #rust testing #CI/CD gating #code review pipeline

Ready to run

npx skills add https://github.com/monktui/git-review --skill quality-gates-monktui

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: quality-gates
Source: https://github.com/monktui/git-review/tree/main/.claude/skills/quality-gates
Command: npx skills add https://github.com/monktui/git-review --skill quality-gates-monktui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents “nearly working” changes from slipping into your repo by defining a clear definition of done and a repeatable technical-lead review pipeline aligned with CI and local gating.

Core Features & Use Cases

Definition of Done checklist covering tests, formatting, linting, API documentation, and safe error handling.
Deterministic build verification workflow using standard Rust commands to validate code quality before review and commit.
Hook + pipeline integration guidance for validating hook-script changes locally and optionally enforcing review readiness with git-review gate check in CI.

Quick Start

Use quality-gates to confirm your change meets the team’s definition of done by running the full Rust verification set, then validating hook changes with the provided hook test script when applicable.

Frequently Asked Questions about quality-gates

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

FAQPage Schema

How do I enforce a definition of done for Rust code before merging?▼

A CI/CD gating pipeline validates Rust code changes by running deterministic build verification commands including cargo test, cargo clippy, and cargo fmt checks. This enforces review readiness for commits and diffs before they reach the merge stage.

How do I set up pre-commit hooks for Rust testing and linting?▼

A technical-lead review pipeline applies to Rust development workflows by defining done criteria and executing a deterministic build verification workflow. It aligns local hook testing with CI/CD gating to enforce review readiness for implementation completion.

Can I use cargo clippy and cargo fmt checks to gate code review readiness?▼

Yes, you can use cargo clippy and cargo fmt checks to gate code review readiness by integrating them into a verification pipeline. This satisfies deterministic execution requirements and ensures diffs meet quality standards before tech-lead review.

What is the best way to prevent unreviewed Rust commits from slipping into the repo?▼

The best way to prevent unreviewed Rust commits from slipping into the repo is to define a clear definition of done and enforce a repeatable tech-lead review pipeline. You optionally enforce review readiness using gate-check behavior in CI/CD.