mcpField
L
linter-docs

linter-docs

github.com/zernieTesting & quality152.0k installsUpdated 2d ago
Repository

About linter-docs

Reference material for the linters cross-referenced by vigiles. It helps users author or troubleshoot `enforce()` rules with details on rule names, AST selectors, and configuration; the skill is opened manually and does not activate on its own.

Key features

  1. 01ESLint, Ruff, and Pylint references
  2. 02RuboCop, Stylelint, and Clippy references
  3. 03Rule names and AST selector details
  4. 04Configuration and auto-fix notes
  5. 05Cross-references for additional linters

Use cases

  1. 01Find a linter rule for an `enforce()` rule
  2. 02Diagnose a rule reported missing or disabled
  3. 03Check a linter's configuration options

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/zernie/vigiles --skill linter-docs

After installing, type/linter-docsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

clippy.md
eslint.md
pylint.md
rubocop.md
ruff.md
stylelint.md

Details

From the project README

Reference material for the linters vigiles cross-references. Open the file for the linter you're working with when you need exact rule names, AST selectors, or config details to author an enforce() rule (or diagnose why one is reported missing or disabled).

LinterReference
ESLinteslint.md — plugin table, AST selectors, type-aware rules, auto-fix
Ruffruff.md — 800+ reimplemented rules, selection, auto-fix, pyproject config
Pylintpylint.md — plugin table, astroid AST, type inference, custom checkers
RuboCoprubocop.md — gem table, node pattern DSL, auto-correct, custom cops
Stylelintstylelint.md — plugin table, PostCSS AST, custom rules, SCSS
Clippyclippy.md — Rust lint groups and configuration

JVM/Go linters (detekt, ktlint, Checkstyle, golangci-lint) and Cedar are cross-referenced by enforce() but have no deep-dive file here yet — their capabilities, config surfaces, and known limits (e.g. ktlint is format-only, Checkstyle enabled-state is whitelist-only) are documented in docs/linter-support.md.

These are read by the strengthen and edit-spec skills when matching a guidance rule to a real linter rule. This skill is user-invoked (a reference, not an action), so it never fires on its own — open the relevant file directly.

Comments

Markdown supported