ml-lint

Run Ruff formatting, lint, and optional ty type checks on Python code.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/nishide-dev/claude-code-ml-research --skill ml-lint
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ml-lint
Source: https://github.com/nishide-dev/claude-code-ml-research/tree/main/skills/ml-lint
Command: npx skills add https://github.com/nishide-dev/claude-code-ml-research --skill ml-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you find and fix code-quality problems early by running consistent formatting, linting, and (when applicable) type checks.

Core Features & Use Cases

  • Ruff formatting checks: Verify code follows the repository’s formatting rules so diffs stay clean and readable.
  • Ruff lint checks (optionally auto-fix): Detect common issues like unused imports, undefined names, and style violations before they become bugs.
  • Type checking with ty: Surface type-hint mismatches to improve maintainability and reduce runtime surprises; useful for larger or more strictly typed codebases.

Example use case: before a pull request, run the checks across the whole project to ensure formatting, linting, and typing are all clean so CI is less likely to fail.

Quick Start

Run the ml-lint skill to lint, format, and type-check your project for readiness before committing or opening a pull request.

Frequently Asked Questions about ml-lint

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

FAQPage Schema
How do I run Python lint and type checks before a pull request?▼

Run Python lint and type checks before a pull request by executing Ruff formatting, Ruff lint rules, and optional ty-based type checking across your chosen scope to ensure formatting and typing are clean so CI is less likely to fail.

Can I auto-fix Ruff lint issues and type check my whole repository?▼

You can auto-fix Ruff lint issues and type check your whole repository by applying Ruff formatting checks, Ruff lint rules with optional auto-fix, and ty-based type checking across the whole-repo, directory, file, or changed-files-only workflows.

What do I need to run Ruff formatting and linting in a pre-commit hook?▼

To run Ruff formatting and linting in a pre-commit hook, you need the uv tool installed, which is required to execute the ruff and ty commands, interpret exit codes, and optionally support auto-fix and strict modes.

Does this approach support checking only changed files instead of the whole project?▼

Checking changed files instead of the whole project is supported through changed-files-only workflows, allowing you to apply Ruff formatting, Ruff lint rules, and optional ty-based type checking directly to modified code for faster validation.

What is the best way to enforce Python code quality in CI pipelines?▼

The best way to enforce Python code quality in CI pipelines is to run comprehensive checks applying Ruff formatting, Ruff lint rules, and optional ty-based type checking to catch lint and type issues before they ship.

Why use ty for type checking alongside Ruff in Python projects?▼

Use ty for type checking alongside Ruff to surface type-hint mismatches and reduce runtime surprises, while Ruff handles formatting and lint rules to detect unused imports, undefined names, and style violations.