lint

Collect and fix linting errors and build failures across Node.js and Java projects.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/nabi-chan/dotfiles --skill lint-nabi-chan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/nabi-chan/dotfiles/tree/main/dot_claude/skills/lint
Command: npx skills add https://github.com/nabi-chan/dotfiles --skill lint-nabi-chan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically collects and fixes linting errors and build failures in your code, ensuring code quality and project stability.

Core Features & Use Cases

  • IDE Diagnostics: Gathers diagnostic information directly from your IDE.
  • Automated Linting: Runs linters like ESLint for Node.js projects and build commands for Java projects.
  • Error Correction: Attempts to automatically fix identified errors, prioritizing those that can be resolved with tools like eslint --fix.
  • Use Case: When you encounter a JavaScript error flagged by ESLint, this Skill can automatically apply the fix, saving you the manual effort of correcting the code.

Quick Start

Use the lint skill to collect and fix all linting errors in the current project.

Frequently Asked Questions about lint

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

FAQPage Schema
How do I automatically fix ESLint errors in my Node.js project?

To automatically fix ESLint errors in a Node.js project, this Skill collects IDE diagnostics and applies automated corrections, prioritizing issues resolvable with the `eslint --fix` command to ensure code quality.

Can I resolve Java build failures using Gradle and Maven automatically?

Yes, you can resolve Java build failures automatically. This Skill runs command-line build commands via Gradle and Maven, identifies the build errors, and iteratively attempts corrections to restore project stability.

What is the best way to collect and resolve code linting issues across different project types?

The best way to collect and resolve code linting issues across various project types is by leveraging IDE diagnostics and command-line tools like ESLint, Gradle, and Maven to identify and rectify code quality issues iteratively.

Does fixing build errors stop if the code keeps failing repeatedly?

Yes, when fixing build errors, the process involves iterative cycles of error correction and verification, but it enforces a strict limit on retries to ensure efficient resolution and prevent infinite loops.

How does IDE diagnostic integration work for debugging code quality issues?

IDE diagnostic integration works for debugging code quality issues by directly gathering diagnostic information from your IDE, which is then used alongside command-line linters to identify and automatically rectify flagged errors.