lint-check

Lint changed frontend, Python, and config files with ESLint, Prettier, Ruff, and validators.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/stars-end/affordabot --skill lint-check-stars-end
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-check
Source: https://github.com/stars-end/affordabot/tree/main/.claude/skills/lint-check
Command: npx skills add https://github.com/stars-end/affordabot --skill lint-check-stars-end

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensuring code quality and adherence to style guides before committing can be a manual, time-consuming process, leading to inconsistent code and CI failures.

Core Features & Use Cases

  • Fast, Targeted Linting: Runs quick linting checks on only changed files, providing rapid feedback (under 5 seconds) without running a full suite.
  • Multi-Language Support: Automatically applies appropriate linters (ESLint, Prettier, Ruff, MyPy, JQ, Yamllint) based on file type (TypeScript, Python, JSON, YAML).
  • Clear Issue Reporting: Presents linting failures with file paths and line numbers, guiding you to fix issues efficiently.
  • Use Case: Before committing your changes, simply say "lint my code" to quickly identify and fix any formatting or quality issues, preventing CI failures.

Quick Start

To quickly check your code for formatting and quality issues before committing, simply say: "lint my code"

Frequently Asked Questions about lint-check

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

FAQPage Schema
How do I check code quality before committing changes?

Run linting checks on only your changed files to catch formatting and quality issues fast. This Skill performs targeted validation using ESLint and Prettier for TypeScript/JavaScript, Ruff for Python, and validators for JSON and YAML—completing in under 5 seconds and flagging issues by file and line number without auto-fixing.

What file types can this linting tool validate?

Linting validation covers frontend files (TypeScript, JavaScript, TSX, JSX), Python backend files, and configuration files (JSON, YAML). The Skill automatically selects the appropriate linter—ESLint, Prettier, Ruff, MyPy, JQ, or Yamllint—based on file extension.

Can I run linting checks only on changed files instead of the entire codebase?

Yes, this Skill analyzes only staged or unstaged changed files rather than your whole project. This targeted approach delivers rapid feedback under 5 seconds, making it ideal for pre-commit validation while deferring comprehensive checks to CI.

Does this tool auto-fix formatting issues or just report them?

This Skill reports linting and formatting failures with specific file paths and line numbers for manual fixing. It does not auto-fix issues, ensuring you review and approve all changes before commit.

Why should I lint locally before pushing to CI?

Pre-commit linting catches style and quality issues early, preventing CI failures and reducing feedback loops. This Skill's fast, file-scoped validation lets you fix problems immediately in your workflow rather than discovering them downstream.

Does this support Python type checking with mypy?

Yes, Python validation includes Ruff for linting and optionally integrates MyPy for type checking. Both tools apply to changed Python files, giving you flexible quality gates before commit.