lint

Run Ruff, Pyright, and Ty on git-changed Python files and consolidate findings.

1|Updated Aug 18, 2025

Search Tags:#ruff #static-analysis #lint #report #pyright #ty #changed-files

Ready to run

npx skills add https://github.com/abhinav8888/dot-files --skill lint-abhinav8888

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/abhinav8888/dot-files/tree/main/claude/.claude/skills/lint
Command: npx skills add https://github.com/abhinav8888/dot-files --skill lint-abhinav8888

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of running multiple linters on files that have changed, consolidating results into a single, actionable report to speed up code quality feedback.

Core Features & Use Cases

Unified linting: runs Ruff, Pyright, and Ty on changed files for consistency.
Change-driven: automatically determines which files to lint based on git diffs.
Report consolidation: compiles findings from all tools into a single summary for quick remediation.

Quick Start

Lint the changed files and review the unified report.

Frequently Asked Questions about lint

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

FAQPage Schema

How do I run static analysis on changed Python files in a git repository?▼

To lint changed Python files, the Skill detects modified files via git diffs and runs static analysis tools on them. It then compiles the results from all tools into a single, actionable summary report.

How do I combine Ruff and Pyright reports into a single output?▼

Combining Ruff and Pyright reports is handled by running both tools on changed files and consolidating their findings. The Skill produces a unified lint report that includes syntax errors, type issues, and formatting concerns in one output.

Do I need to install Ruff and Pyright before linting changed files?▼

Yes, you need Ruff, Pyright, and Ty installed in your environment before linting changed files. The Skill requires these static analysis tools to be present so it can execute them and compile their findings into a unified report.

Can I use this linting approach in CI and pre-commit hooks?▼

Yes, you can use this linting approach in CI pipelines, pre-commit hooks, or local development. The Skill applies static analysis to changed Python files by detecting git diffs, making it suitable for automated code quality checks.

What is the best way to lint only Python code that has changed?▼

The best way to lint only changed Python code is to use a change-driven approach that detects modified files via git diffs. This Skill automatically determines which files to lint, ensuring static analysis runs exclusively on updated code.

Why does the unified lint report show syntax errors and formatting concerns together?▼

The unified lint report shows syntax errors and formatting concerns together because it consolidates findings from Ruff, Pyright, and Ty into a single summary. This change-driven approach compiles all static analysis results for quick remediation.