python-code-quality

Orchestrates ruff linting, formatting, and ty type checking across pre-commit and CI pipelines.

2|Updated May 9, 2026
One-click install
npx skills add https://github.com/Manuel-Gartenkrot-Casal/AfterDrive_Intelligence --skill python-code-quality-manuel-gartenkrot-casal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: python-code-quality
Source: https://github.com/Manuel-Gartenkrot-Casal/AfterDrive_Intelligence/tree/main/.agents/skills/python-code-quality
Command: npx skills add https://github.com/Manuel-Gartenkrot-Casal/AfterDrive_Intelligence --skill python-code-quality-manuel-gartenkrot-casal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a complete Python quality stack requires coordinating multiple tools (ruff, ty, basedpyright, vulture) across pre-commit hooks and CI, and it is easy to misconfigure how they fit together. This Skill acts as an orchestration index that routes you to the right focused configuration guidance for each tool. ## Core Features & Use Cases - Stack Orchestration: Explains how ruff lint, ruff format, and ty type checking work together as one quality gate. - Routing Table: Directs you to focused guidance for lint rules, formatting, type checking, dead-code detection, and testing. - Pre-commit & CI Wiring: Provides a ready pre-commit configuration running ruff-check, ruff-format, and ty together, plus the standard CI quality gate commands. - Use Case: When starting a new Python project, use this Skill to stand up lint + format + type-check in pre-commit and CI in one pass instead of configuring each tool in isolation. ## Quick Start Ask the assistant to set up a complete Python code quality stack with ruff and ty wired into pre-commit and CI for your project.

Frequently Asked Questions about python-code-quality

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

FAQPage Schema
How do I set up ruff and ty together in pre-commit?▼

Add the ruff-pre-commit repo with ruff-check and ruff-format hooks, plus the astral-sh/ty repo with the ty hook, to your .pre-commit-config.yaml. This runs linting, formatting, and type checking on every commit.

What is the difference between ruff lint and ruff format?▼

Ruff lint checks code for rule violations and can auto-fix many of them, while ruff format rewrites code style such as quote style and line length. Both run as separate pre-commit hooks and as separate CI steps.

Should I use ty or basedpyright for Python type checking?▼

Both are supported type checkers in this stack. The Skill routes you to dedicated guidance for each: ty-type-checking for ty and basedpyright-type-checking for basedpyright, so you can configure strictness rules for whichever you choose.

What commands run in a typical Python CI quality gate?▼

A typical CI quality gate runs three steps: ruff check for linting, ruff format --check to verify formatting, and ty check for type checking. These mirror the pre-commit hooks so local and CI behavior stay consistent.

When should I use this orchestration skill instead of a single-tool guide?▼

Use it when standing up a full quality stack or reasoning about how lint, format, and type-check fit together. For tuning one tool, such as ruff rule selection or formatter quirks, use the focused single-tool guidance instead.