linter

Detect and fix code style issues in recently edited files using project linters.

3|1|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/Probably-Group/Dev-AID --skill linter-probably-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linter
Source: https://github.com/Probably-Group/Dev-AID/tree/main/.dev-aid/skills/core/linter
Command: npx skills add https://github.com/Probably-Group/Dev-AID --skill linter-probably-group

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you catch and fix code-quality issues immediately instead of discovering them late during review or CI runs.

Core Features & Use Cases

  • Auto-detects the right linter: Runs the project-appropriate formatter/linter based on common config files across JavaScript/TypeScript, Python, Rust, Go, and shell scripts.
  • Targets only changed code: Applies linting to the file(s) you just edited to keep feedback fast and focused.
  • Supports safe auto-fix: Uses auto-fix flags when supported and reports any remaining unfixable issues clearly.
  • Use case: While working in a TypeScript app, it detects ESLint/Prettier/biome, flags unused variables or missing return types, and suggests or applies fixes right after you save.

Quick Start

Ask the AI to lint and auto-fix the files you just changed, and then show any remaining issues it cannot fix.

Frequently Asked Questions about linter

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

FAQPage Schema
How do I automatically lint and fix code style issues in recently edited files?

You can lint only changed files by triggering the tool on your recently edited code; it detects your existing project linter configurations like ESLint or Ruff, runs targeted checks, and applies safe auto-fixes for immediate code style feedback.

Does auto-fixing linting errors work with ESLint and Prettier for TypeScript?

Yes, auto-fixing linting errors works with ESLint and Prettier for TypeScript. The tool detects these standard configuration files, applies supported auto-fix flags to correct issues, and reports any remaining unfixable problems.

What programming languages and linters are supported for code quality checks?

Supported code quality checks cover JavaScript, TypeScript, Python, Rust, Go, Ruby, and Shell scripting. The tool runs the appropriate project linter, such as ESLint, Ruff, or ShellCheck, by detecting standard configuration files in your repository.

Can I run shell script linting with ShellCheck on only the files I just changed?

Yes, you can run ShellCheck linting on only the files you just changed. The tool targets recently edited files exclusively, ensuring fast and focused shell script linting feedback while skipping ignored paths and non-code files.

Why is code linting skipping my configuration files and non-code paths?

Code linting skips configuration files and non-code paths by design to keep feedback fast and focused on actual source code. The tool intentionally bypasses ignored paths, absent configs, and non-code files during the changed-file-only linting execution.