---

name: quality-gates description: Python code quality gates script for linting, type checking, complexity analysis, and testing before commits. Use when enforcing consistent code quality across Python projects with fast (unit-tests) or comprehensive (all-tests) modes. license: Complete terms in LICENSE.txt

Quality Gates

Overview

Project-agnostic bash script enforcing Python code quality gates using ruff, pyrefly, radon, hypothesis, pytest, and markdownlint. Three execution modes provide flexibility for different workflows: unit-tests for fast feedback, all-tests for comprehensive pre-merge validation, no-tests for static analysis only.

When to Use

Before committing Python code to enforce consistent quality checks across projects without directory structure assumptions.

Modes

Quick Start

Running quality gates:

Make sure uv is installed.

Copy# Fast feedback: lint + type check + unit tests
.claude/skills/quality-gates/scripts/quality-gates.sh unit-tests

# Pre-merge: everything including integration tests
.claude/skills/quality-gates/scripts/quality-gates.sh all-tests

# Quick static checks only
.claude/skills/quality-gates/scripts/quality-gates.sh no-tests

Implementation Details

• Script: scripts/quality-gates.sh - Uses uv/uvx for tool management
• Excluded directories: tests, test, docs, doc, examples, scripts, build, dist, .venv, venv, .tox, .git, node_modules, pycache, *.egg-info
• Graceful fallbacks: Skips missing tools without failing

Common Anti-Patterns

Red Flags

Stop and re-evaluate if you're:

• Skipping all checks
• "This time is different"
• "Good enough for now"
• Rationalizing under deadline pressure

All of these suggest running the script with the appropriate mode.