run-linters

Run Black, flake8, mypy, and pyright to check Python code quality.

21|6|Updated Dec 15, 2022

Search Tags:#code quality #automation #linting #python #ci

Ready to run

npx skills add https://github.com/CERTCC/Vultron --skill run-linters-certcc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: run-linters
Source: https://github.com/CERTCC/Vultron/tree/main/.agents/skills/run-linters
Command: npx skills add https://github.com/CERTCC/Vultron --skill run-linters-certcc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Developers and maintainers often struggle with ensuring code adheres to style and quality standards before committing. This Skill automates the process of running multiple linters, enabling consistent code quality checks.

Core Features & Use Cases

Unified Linting: Runs Black for code formatting, flake8 for style, mypy and pyright for type checking.
Pre-commit Validation: Ensures code is clean and compliant before staging code for commits or deployment.
Use Case: Automatically verifying code quality locally before pushing changes to a shared repository or triggering CI to prevent failures.

Quick Start

Invoke the 'run-linters' skill to check your repository for formatting, style, and type errors before committing.

Frequently Asked Questions about run-linters

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

FAQPage Schema

How do I automate Python code quality checks before committing?▼

Automate Python code quality checks before committing by invoking a unified linting process that runs formatting, style, and type-checking tools. This validates your codebase locally to ensure adherence to safety standards before staging changes.

What's the best way to run multiple Python linters in a CI/CD pipeline?▼

The best way to run multiple Python linters in a CI/CD pipeline is using an automated execution skill that sequentially processes Black, flake8, mypy, and pyright. This prevents CI failures by validating code quality and compliance before deployment.

Do I need the uv environment to run automated linting tools?▼

Yes, you need the uv environment to run these automated linting tools. The unified linting process explicitly requires the uv environment to execute Black, flake8, mypy, and pyright for maintaining clean and error-free codebases.

Can I use this automated linting skill for pre-commit validation?▼

Yes, you can use this automated linting skill for pre-commit validation. It ensures code is clean and compliant by automatically verifying formatting, style, and type errors before you stage code for commits or trigger CI pipelines.

Why does automated Python type checking require both mypy and pyright?▼

Automated Python type checking uses both mypy and pyright to provide comprehensive static analysis coverage. Running both tools ensures stricter adherence to style and safety standards by catching different categories of type errors in your codebase.

When should I not use automated linting for Python development?▼

You should not use automated linting when your Python project lacks a uv environment setup or when immediate deployment is required without pre-commit validation. It is designed for ensuring compliance in CI/CD pipelines and local development, not for bypassing quality checks.