check

Run Makefile quality gates for Python linting and type checks.

Updated May 24, 2025
One-click install
npx skills add https://github.com/lemeb/python-library-cookiecutter --skill check-lemeb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/lemeb/python-library-cookiecutter/tree/main/%7B%7Bcookiecutter.project_slug%7D%7D/.claude/skills/check
Command: npx skills add https://github.com/lemeb/python-library-cookiecutter --skill check-lemeb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Linting and Type-Checking quality gates help ensure Python code meets formatting, style, and type correctness, catching issues before commits.

Core Features & Use Cases

  • Auto-fixes simple formatting and minor issues with make check-fix
  • Enforces full verification by running make check and make check-strict-all
  • Provides guidance from dev/checking.md to resolve and learn from failures

Quick Start

Run make check-fix to auto-fix issues, then run make check and make check-strict-all to ensure code passes all quality gates before committing.

Frequently Asked Questions about check

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

FAQPage Schema
How do I automate Python linting and type checking before commits?

You can automate Python linting and type checking before commits by running Makefile quality gates like make check-fix, make check, and make check-strict-all to enforce static analysis and formatting rules.

What is the best way to fix formatting and style issues in a Python project?

The best way to fix formatting and style issues is to run make check-fix, which auto-fixes simple formatting and minor linting problems before enforcing strict type checking rules on your codebase.

How do I enforce strict static analysis and type checking quality gates?

You enforce strict static analysis and type checking quality gates by running make check and then make check-strict-all, iterating until all formatting, style, and type correctness checks pass.

Does this automated checking workflow require a Makefile setup?

Yes, this automated checking workflow requires a Makefile setup and guidance documentation in dev/checking.md to run the make check-fix, make check, and make check-strict-all targets for Python projects.

Why does make check-strict-all fail after running make check-fix?

Make check-strict-all fails after make check-fix because auto-fixing only resolves simple formatting and minor issues, leaving complex type checking or static analysis violations that require manual code corrections.

Can I use this to run quality gates for non-Python projects?

No, you cannot use this for non-Python projects, because the quality gates, Makefile targets, and checking documentation are specifically designed to enforce Python linting and type checking standards.