audit-less

Scan LESS stylesheets for variable errors and report fixes.

666|77|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/jhd3197/ServerKit --skill audit-less
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-less
Source: https://github.com/jhd3197/ServerKit/tree/main/.claude/skills/audit-less
Command: npx skills add https://github.com/jhd3197/ServerKit --skill audit-less

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automatically scans LESS stylesheets to identify and report common, build-breaking errors related to variable usage, ensuring a smoother frontend development workflow.

Core Features & Use Cases

  • Undefined Variable Detection: Catches misspelled or missing LESS variables.
  • CSS Custom Property Validation: Ensures CSS variables are not incorrectly used in LESS compile-time functions.
  • Pattern Matching: Enforces consistent naming conventions for variables.
  • Use Case: A developer pushes a change with a new LESS file that accidentally uses a CSS custom property in a LESS function, causing the build to fail. This Skill would flag the error before deployment.

Quick Start

Run the audit-less skill on the frontend/src/styles directory.

Frequently Asked Questions about audit-less

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

FAQPage Schema
How do I fix undefined LESS variables causing build failures?

To fix undefined LESS variables, scan your stylesheets to identify misspelled or missing variables causing build failures. The scan reports issues with file, line number, and suggested fixes for smoother frontend development.

Why does using a CSS custom property in a LESS function break the build?

Using a CSS custom property in a LESS compile-time function breaks the build because LESS functions expect LESS variables. Scanning stylesheets validates usage and flags incorrectly placed CSS variables before deployment.

Can I enforce consistent variable naming conventions in LESS stylesheets?

Yes, you can enforce consistent variable naming conventions in LESS stylesheets. Pattern matching scans for incorrect variable name patterns and reports issues with file and line number to ensure consistency.

How do I audit LESS files for variable errors before deployment?

Audit LESS files for variable errors by running a scan on your styles directory. The scan detects undefined variables, naming pattern issues, and CSS custom property misuse, reporting each issue with suggested fixes.

What is the best way to find CSS variables incorrectly used in LESS compile-time functions?

The best way to find CSS variables incorrectly used in LESS compile-time functions is to scan stylesheets for custom property validation. This flags CSS variables used in LESS functions, preventing build failures.

Does LESS variable scanning report the exact file and line number of errors?

Yes, LESS variable scanning reports the exact file and line number of errors. It identifies undefined variables, incorrect naming patterns, and CSS custom property misuse, providing suggested fixes for each issue.