lint

Detect and auto-fix code quality issues with ESLint, Prettier, or Deno.

20|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/HerbertJulio/specialist-agent --skill lint-herbertjulio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/HerbertJulio/specialist-agent/tree/main/skills/lint
Command: npx skills add https://github.com/HerbertJulio/specialist-agent --skill lint-herbertjulio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Linting stabilizes code quality by automatically detecting style and correctness issues and applying safe fixes to speed up CI and everyday development.

Core Features & Use Cases

  • Detect linting errors and enforce consistent style across a codebase.
  • Apply safe fixes automatically where possible and report remaining issues for manual review.
  • Integrate with common tooling (ESLint, Prettier, Deno) and npm scripts for CI workflows.

Quick Start

Run the lint workflow on your project to auto-fix issues and report remaining problems.

Frequently Asked Questions about lint

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

FAQPage Schema
How do I auto-fix linting errors in my codebase?

To auto-fix linting errors, you can run a lint workflow that detects style and correctness issues across your project and safely applies non-breaking corrections automatically.

Can I use ESLint and Prettier together to enforce code quality?

Yes, you can use ESLint and Prettier together; the linting process detects existing configuration files, determines the appropriate tooling, and executes fixes to enforce consistent code quality.

How do I run lint checks in CI workflows without breaking the build?

To run lint checks in CI workflows safely, the process prioritizes safe, non-breaking changes by applying automatic fixes and reporting remaining issues for manual review.

Does auto-fixing lint issues work with Deno projects?

Yes, auto-fixing lint issues works with Deno projects; the tooling detects configuration files, determines the linter, and executes fixes across various supported environments.

What is the best way to detect and report remaining code style issues?

The best way to detect and report code style issues is to lint the codebase to automatically apply safe corrections, then generate a report of remaining problems for manual review.