code-quality

Run code quality checks. Use after making code changes, before commits, or when asked to check code quality.

⭐3stars🔀0forks📁View on GitHub🕐Updated Dec 21, 2025

When & Why to Use This Skill

This Claude skill automates essential code quality checks, including type checking and linting, to ensure robust and maintainable software development. By integrating these automated tools, it helps developers identify errors early, enforce coding standards, and streamline the pre-commit workflow for higher software reliability.

Use Cases

  • Pre-commit Validation: Run comprehensive checks before committing code to ensure no syntax or type errors are introduced into the repository.
  • Automated Code Formatting: Utilize the lint-fix command to automatically resolve stylistic issues and maintain a consistent codebase without manual intervention.
  • Continuous Quality Monitoring: Perform regular health checks on the codebase to detect potential bugs and technical debt early in the development lifecycle.
  • Type Safety Assurance: Execute dedicated type-checking commands to verify data integrity and prevent runtime type errors in complex applications.
namecode-quality
descriptionRun code quality checks. Use after making code changes, before commits, or when asked to check code quality.
allowed-toolsBash, Read, Grep, Glob

Code Quality Checks

Run code quality checks after making code changes.

Commands

# Full check (type checking + linting)
./start.sh check

# Type checking only
./start.sh typecheck

# Linting only
./start.sh lint

# Linting with auto-fix
./start.sh lint-fix

Workflow

  1. Make code changes
  2. Run ./start.sh check
  3. If lint errors can be auto-fixed, run ./start.sh lint-fix
  4. Fix remaining errors manually
  5. Re-run check to verify