
Python Code Quality
- 903 installs
- 49 repo stars
- Updated August 4, 2026
- laurigates/claude-plugins
python-code-quality is a Python skill that orchestrates Ruff linting, formatting, and Ty type checking with pre-commit and CI integration for developers standardizing a full quality stack.
About
python-code-quality is a laurigates Claude plugin skill last modified 2026-05-29 that routes agents across the Python quality stack without duplicating per-tool command references. It coordinates Ruff for linting and formatting, Ty for type checking, and hooks for pre-commit and CI when users mention ruff, ty, linting, formatting, or Python code style. The skill is user-invocable false and uses Bash, Read, Grep, and Glob to inspect projects and wire the combined lint-format-type-check workflow. Developers reach for python-code-quality when setting up or reasoning about the entire Python quality pipeline at once rather than tuning a single tool in isolation.
- Combines Ruff (lint + format) and Ty (type checking) into one ready-to-use quality workflow
- Sets up pre-commit hooks and CI/CD quality gates in a single invocation
- Provides quick reference commands for common lint, fix, format, and rule-selection tasks
- Compares Ruff, Ty, and basedpyright at a high level before tool selection
- 3 focused sibling skills for narrow tuning (ruff-linting, ruff-formatting, ty-type-checking)
Python Code Quality by the numbers
- 903 all-time installs (skills.sh)
- +24 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #156 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/laurigates/claude-plugins --skill python-code-qualityAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 903 |
|---|---|
| repo stars | ★ 49 |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 4, 2026 |
| Repository | laurigates/claude-plugins ↗ |
How do you set up Ruff and Ty together?
Instantly wire together Ruff linting, formatting, and Ty type checking into a complete Python quality stack with pre-commit and CI integration.
Who is it for?
Developers standardizing an entire Python lint-format-type-check pipeline with Ruff, Ty, pre-commit, and CI in one pass.
Skip if: Developers tuning only one Ruff rule or a single Ty error should use the focused per-tool skill instead of the orchestration index.
When should I use this skill?
The user mentions ruff, ty, Python linting, formatting, type checking, pre-commit, or setting up the full Python quality stack.
What you get
Ruff and Ty configuration, pre-commit hooks, and CI quality gate integration.
- Ruff configuration
- Ty type-check setup
- Pre-commit and CI integration
By the numbers
- Skill metadata shows modified date 2026-05-29
Files
Python Code Quality
Orchestration index for the Python quality stack. This skill routes to the focused skills that own each tool — it does not restate their commands. Reach for it when setting up or reasoning about the whole stack (lint + format + type-check + tests) at once; reach for a focused skill when tuning one tool.
When to Use This Skill
| Use this skill when... | Use a focused sibling instead when... |
|---|---|
| Standing up a complete quality stack for a new project | Tuning only ruff lint rule selection — use ruff-linting |
| Reasoning about how the tools fit together / comparing them | Configuring only ruff formatter quirks — use ruff-formatting |
| Wiring lint + type-check into pre-commit and CI together | Configuring strict type-checker rules — use ty-type-checking or basedpyright-type-checking |
Routing Table
| Concern | Focused skill |
|---|---|
| Lint rules, rule selection, auto-fix | python-plugin:ruff-linting |
| Code formatting (quote style, line length) | python-plugin:ruff-formatting |
| Editor / pre-commit / CI / Docker wiring for ruff | python-plugin:ruff-linting → its REFERENCE.md |
| Type checking with ty | python-plugin:ty-type-checking |
| Type checking with basedpyright | python-plugin:basedpyright-type-checking |
| Dead-code detection | python-plugin:vulture-dead-code |
| Test quality / coverage | python-plugin:python-testing, python-plugin:pytest-advanced |
| Modern type-hint syntax and idioms | python-plugin:python-development |
| Adding the tools to a project | python-plugin:uv-project-management |
Full Stack at a Glance
The one thing this index owns: the tools running together in pre-commit. For each tool's flags and config, follow the routing table above.
# .pre-commit-config.yaml — ruff (lint + format) and ty together
repos:
- repo: https://github.com/astral-sh/ruff-pre-commit
rev: v0.14.0
hooks:
- id: ruff-check
args: [--fix]
- id: ruff-format
- repo: https://github.com/astral-sh/ty
rev: v0.0.10
hooks:
- id: tyA typical CI quality gate runs the same three steps: ruff check, ruff format --check, ty check. See ruff-linting § CI/CD Integration and ty-type-checking for the runnable forms.
References
- Ruff: <https://docs.astral.sh/ruff/>
- ty: <https://docs.astral.sh/ty/>
Related skills
FAQ
What tools does python-code-quality orchestrate?
python-code-quality coordinates Ruff for linting and formatting plus Ty for type checking, and helps integrate both into pre-commit hooks and CI. It routes to focused skills when tuning a single tool.
When should developers use python-code-quality versus a focused skill?
Use python-code-quality when setting up or reviewing the full Python lint-format-type-check stack at once. Use focused per-tool skills when adjusting individual Ruff rules or specific Ty diagnostics.
Is Python Code Quality safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.