lint-components

Validate Garura components with structural and semantic lint rules, producing categorized reports.

3|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill lint-components
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-components
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/skills/lint-components
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill lint-components

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps prevent broken or inconsistently structured Garura components by automatically validating plays, agents, and skills against structural and semantic rules before integration or release.

Core Features & Use Cases

  • Deterministic component linting: Runs the Node.js linter against core/components to produce a structured, machine-readable report.
  • Quality-profile-aware severity: Maps lint severities (error/warning/info) into blocker vs informational classifications using the repo’s quality profile.
  • Cross-reference friendly reporting: Captures file-level violations with rule identifiers, messages, and line numbers for actionable remediation.

Quick Start

Ask to run the lint-components skill against your repository root and write the lint report artifact to your chosen STM output path.

Frequently Asked Questions about lint-components

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

FAQPage Schema
How do I validate component structure and cross-references before release?

Static analysis for component validation runs structural, semantic, and cross-reference lint rules against your components directory. It produces a categorized report artifact capturing file-level violations with rule identifiers, messages, and line numbers for actionable remediation.

How does quality-profile-based classification map linting errors and warnings?

Quality-profile-based classification maps standard lint severities like error, warning, and info into blocker versus informational categories. This mechanism applies your repository's quality profile to enforce maintainability and security targets across environments during CI-style verification.

Do I need Node.js to run static analysis on plays, agents, and skills?

Yes, you need Node.js installed to execute the linter and parse JSON output for this static analysis. The linter execution specifically validates plays, agents, and skills located under your core/components directory path.

What is the best way to generate a machine-readable lint report artifact for CI?

The best way to generate a machine-readable lint report artifact for CI is executing a Node.js linter that outputs structured JSON. This deterministic component linting process captures file-level violations categorized by your repository's quality profile.

Why does my component validation report show different severity levels than the linter output?

Component validation reports show different severity levels because the linter applies quality-profile-aware severity mapping. It translates standard error, warning, and info lint severities into blocker and informational classifications based on your repository's specific quality profile rules.