lint-guard

Detect languages, configure per-language linters, and run complexity checks.

23|7|Updated Sep 8, 2025
One-click install
npx skills add https://github.com/pvillega/claude-templates --skill lint-guard
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lint-guard
Source: https://github.com/pvillega/claude-templates/tree/main/plugins/ct/skills/lint-guard
Command: npx skills add https://github.com/pvillega/claude-templates --skill lint-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many codebases lack consistent, enforceable complexity limits and per-language linter configurations, which leads to hard-to-maintain code and unnoticed complexity regressions; lint-guard automates detection, recommendation, and enforcement of strict complexity rules so teams catch issues early.

Core Features & Use Cases

  • Language detection across repositories to determine which linters are relevant.
  • Recommendation and configuration of strict complexity rules per language and installation guidance for chosen linters.
  • Lint-check mode that runs linters only on changed files, applies safe autofixes where configured, and reports non-autofixable complexity violations without modifying code.
  • Project integration by generating .claude/linters.json and installing a Stop hook to run linters automatically after edits.
  • Use Case: On a multi-language repo, run lint-guard to add strict complexity rules, install linters, and ensure future changes fail CI or developer checks when they exceed thresholds.

Quick Start

Run lint-guard to detect languages, recommend linters, and install strict complexity rules after you approve them.

Frequently Asked Questions about lint-guard

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

FAQPage Schema
How do I enforce strict complexity linting across a multi-language repository?▼

Strict complexity linting across a multi-language repository requires detecting source languages and configuring per-language linters with thresholds. lint-guard automates this detection, recommends linters, and writes strict complexity rules to enforce code quality.

Can I run linters only on changed files to speed up code quality checks?▼

Yes, running linters only on changed files speeds up code quality checks. lint-guard features a lint-check mode that targets changed files, applies configured safe autofixes, and reports non-autofixable complexity violations without modifying the source code.

How do I automatically run linters after code edits using hooks?▼

You can automatically run linters after code edits by registering a Stop hook in your project configuration. lint-guard generates a .claude/linters.json file and installs a Stop hook to execute configured linters automatically following edits.

What is the best way to prevent unchecked complexity regressions in source code?▼

Preventing unchecked complexity regressions requires enforcing strict complexity limits via automated linter configurations and hooks. lint-guard applies strict rules and registers automated hooks to catch complexity issues early before they enter the codebase.

Does lint-guard auto-fix all complexity violations in my code?▼

No, lint-guard does not auto-fix all complexity violations in your code. It applies safe autofix commands only where configured and deliberately avoids auto-fixing non-autofixable complexity violations, reporting them instead.