quality-check

DCRepairCenter's avatarfrom DCRepairCenter

Run comprehensive quality checks including linting, type checking, and tests. Use before committing or when validating code changes.

⭐0stars🔀1forks📁View on GitHub🕐Updated Jan 1, 2026
[Testing and QA]

When & Why to Use This Skill

This Claude skill automates comprehensive code quality assurance by integrating linting, type checking, and automated testing into the development workflow. It ensures codebase health for Python and Rust projects by identifying syntax errors, type mismatches, and logic flaws, helping developers maintain high standards and prevent regressions before code is committed.

Use Cases

  • Pre-commit Validation: Run a full suite of linting and unit tests to ensure code changes meet project standards before pushing to a repository.
  • Automated Bug Detection: Utilize static analysis and type checking (Mypy/Clippy) to catch potential runtime errors and type mismatches early in the development cycle.
  • Codebase Health Audits: Perform comprehensive checks on existing codebases to identify technical debt, unused variables, and gaps in test coverage.
  • Standardized Formatting: Automatically enforce consistent coding styles across a team using tools like Ruff to improve code readability and maintainability.
namequality-check
descriptionRun comprehensive quality checks including linting, type checking, and tests. Use before committing or when validating code changes.

Quality Check Skill

Execute comprehensive quality checks on the codebase.

Commands

# Python linting
make lint          # ruff check (no auto-fix)
make format        # ruff format (auto-fix)

# Type checking
make typecheck     # mypy

# Rust checks
make rust-check    # cargo clippy

# Run tests
make test          # pytest full suite
make test-unit     # unit tests only
make test-cov      # with coverage report

# All checks at once
make check         # lint + typecheck + test

Check Results Interpretation

Ruff Errors

  • E - pycodestyle errors
  • W - pycodestyle warnings
  • F - Pyflakes
  • I - isort
  • B - flake8-bugbear
  • UP - pyupgrade

Mypy Errors

  • Missing type annotations
  • Type mismatches
  • Import errors

Clippy Warnings

  • clippy::unwrap_used - Use ? or expect()
  • clippy::todo - Remove before commit
  • clippy::dbg_macro - Remove debug macros

Focus Areas

  • Type annotation completeness
  • Import organization
  • Unused variables/imports
  • Code complexity
  • Test coverage gaps

Workflow

  1. Run make check to see all issues
  2. Report errors with file:line references
  3. Suggest specific fixes
  4. Prioritize by severity (errors > warnings > style)