quality-enforcer

Automates Django project testing and test-result reporting.

Updated Oct 22, 2025
One-click install
npx skills add https://github.com/stharrold/german --skill quality-enforcer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-enforcer
Source: https://github.com/stharrold/german/tree/main/.claude/skills/quality-enforcer
Command: npx skills add https://github.com/stharrold/german --skill quality-enforcer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pytest, pytest-cov, ruff, mypy, uv, and includes scripts (resource) components.

What problem does it solve?

This Skill mitigates the risk of introducing low-quality code, bugs, or technical debt into the main codebase. It automates the enforcement of critical quality standards, ensuring that all code meets predefined benchmarks before integration, saving time on manual reviews and bug fixing.

Core Features & Use Cases

  • Comprehensive Quality Gates: Automatically checks for 80%+ test coverage, passing tests, successful builds, clean linting (ruff), and clean type checking (mypy).
  • Pre-PR Validation: Designed to run before Pull Request creation, providing immediate feedback on code quality and preventing substandard code from entering the integration pipeline.
  • Semantic Versioning Integration: Works with git-workflow-manager to calculate appropriate semantic version bumps based on code changes, maintaining consistent versioning.
  • Use Case: Before submitting a feature for review, run run_quality_gates.py to get an instant, comprehensive report on your code's quality. If any gate fails, you'll know exactly what to fix, ensuring your PRs are always merge-ready.

Quick Start

Example: Run all quality gates

python .claude/skills/quality-enforcer/scripts/run_quality_gates.py

Frequently Asked Questions about quality-enforcer

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

FAQPage Schema
How do I automate quality checks before creating a pull request?

Automate quality checks by running comprehensive gates that verify test coverage, passing tests, successful builds, linting, and type checking before PR creation. quality-enforcer orchestrates these checks sequentially, providing deterministic exit codes and actionable reporting to catch issues early.

What does a quality gate enforce in CI/CD pipelines?

Quality gates enforce predefined code standards including 80%+ test coverage thresholds, passing test suites, clean linting with ruff, and type safety with mypy. They prevent low-quality code from entering the main codebase by validating all criteria before integration.

Can I run quality checks locally before submitting code?

Yes. Run quality-enforcer's script locally to get immediate, comprehensive feedback on code quality before PR submission. The tool reports exactly which gates fail, letting you fix issues and ensure your PR is merge-ready before pushing.

Does quality-enforcer work with existing Python testing and linting tools?

Yes. quality-enforcer integrates seamlessly with pytest for testing, ruff for linting, mypy for type checking, and uv for build validation. It orchestrates these tools within a unified gate system, eliminating manual execution of separate checks.

What happens when a quality gate fails in the CI/CD workflow?

When a gate fails, quality-enforcer halts execution and returns a deterministic exit code with verbose, actionable reporting showing exactly what failed and why. This prevents substandard code from advancing and guides developers to fix specific issues.

How does quality-enforcer handle semantic versioning in PR workflows?

quality-enforcer integrates with git-workflow-manager to calculate appropriate semantic version bumps based on code changes. This ensures consistent versioning alongside quality validation, maintaining version accuracy as code progresses through gates.