ui-lint

Run ESLint and Stylelint auto-fix passes and export a JSON lint report.

1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/charleshall888/cortex-command --skill ui-lint-charleshall888
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-lint
Source: https://github.com/charleshall888/cortex-command/tree/main/plugins/cortex-ui-extras/skills/ui-lint
Command: npx skills add https://github.com/charleshall888/cortex-command --skill ui-lint-charleshall888

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run ESLint and Stylelint in auto-fix-then-report mode. Write compact results to ui-check-results/lint.json to streamline frontend code quality reviews.

Core Features & Use Cases

  • Automatic fix-and-report linting for frontend codebases.
  • Detects Tailwind plugin configuration and optional rhythmguard Stylelint rules, then reports violations.
  • Produces a structured JSON summary of failures for downstream automation.

Quick Start

Run the UI lint skill to automatically fix lint issues and generate a JSON lint report.

Frequently Asked Questions about ui-lint

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

FAQPage Schema
How do I auto-fix ESLint and Stylelint violations and export a report?

Run a frontend linting skill that applies ESLint and Stylelint auto-fix passes, then generates a structured JSON summary of remaining lint failures and details for downstream automation.

Can I run frontend linting with Tailwind plugin and accessibility checks together?

Yes, frontend linting can target projects with Tailwind plugin configuration and accessibility checks. It detects these setups, applies auto-fixes, and reports any remaining violations in a compact JSON format.

What is the best way to automate UI code quality reviews for downstream pipelines?

Automate UI code quality reviews by running ESLint and Stylelint in auto-fix-then-report mode. This writes compact results to a JSON file, producing a structured summary of failures for seamless pipeline integration.

Does this linting approach work with optional rhythmguard Stylelint rules?

Yes, this linting approach detects optional rhythmguard Stylelint rules during execution. It enforces an auto-fix pass followed by a report pass, including any rhythmguard violations in the final structured JSON lint output.

Where are ESLint and Stylelint failure details written after an auto-fix pass?

ESLint and Stylelint failure details are written to a structured JSON file at the path ui-check-results/lint.json. This compact output captures remaining lint failures and details after the auto-fix pass completes.