linting

Detect file types and run configured linters across multiple languages.

1|Updated Nov 15, 2025
One-click install
npx skills add https://github.com/racurry/neat-little-package --skill linting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linting
Source: https://github.com/racurry/neat-little-package/tree/main/plugins/mr-sparkle/skills/linting
Command: npx skills add https://github.com/racurry/neat-little-package --skill linting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Linting is essential but can be tedious when projects include Python, JavaScript/TypeScript, Markdown, Shell, Ruby, YAML, and JSON. This skill provides a single, polyglot CLI to detect file types, locate project configs, and run appropriate linters automatically.

Core Features & Use Cases

  • Unified workflow: Detects language by file extension, finds project configuration, and runs the right linter(s) in a deterministic, priority-based order
  • Smart tool selection: Prefers tool groups with project config; falls back to sensible defaults
  • Automation-friendly: CLI script at scripts/lint.py can be invoked by agents or commands to lint files on demand

Quick Start

Example user request: Lint a Python file and auto-fix issues using the best available toolchain.

Frequently Asked Questions about linting

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

FAQPage Schema
How do I lint multiple programming languages in a single project?

Polyglot linting runs appropriate linters across Python, JavaScript, TypeScript, Markdown, Shell, Ruby, YAML, and JSON files automatically by detecting file types and project configurations, then applying the right tool for each language without manual setup.

Can I automatically fix linting issues across different file types?

Yes, the linting workflow runs configured linters like ruff, eslint, markdownlint-cli2, shfmt, standard, and prettier with fixes enabled where supported, applying language-specific corrections across your entire codebase.

How does the linter detect which tool to use for each file?

The linter detects file type by extension, locates project configuration files (package.json, pyproject.toml, Gemfile, .git), then selects linters based on a prioritized tool group, falling back to sensible defaults if no config exists.

What's the best way to integrate linting into an automated workflow?

The CLI script at scripts/lint.py can be invoked by agents or commands to lint files on demand, supporting both text and JSON output formats for easy integration into CI/CD pipelines and automation systems.

Does this linting approach work with mixed-language repositories?

Yes, it's designed specifically for polyglot projects containing Python, JavaScript, Markdown, Shell, Ruby, YAML, and JSON files, automatically detecting and linting each language with its appropriate toolchain.