Skip to content

linter-docs

Deep linter reference for authoring or debugging a vigiles enforce() rule — plugin tables, AST selectors, type-aware rules, auto-fix, and edge cases for ESLint, Ruff, Pylint, RuboCop, Stylelint, and Clippy. Use when you need the exact rule name or config for a specific linter, not for running a linter. (JVM/Go linters — detekt, ktlint, Checkstyle, golangci-lint — and Cedar have no deep-dive file yet; their reference lives in docs/linter-support.md.)

2,004
installs
0 up / 0 down, score 0.00
votes
15
repo stars
Updated
less than a month ago
In the catalog since
1 Oct 2026
From
zernie/vigiles
Documentation & Writing
Get it through your agent npx skills add zernie/vigiles@linter-docs

Skill instructions

Rendered from the published SKILL.md, 24 lines.

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).

Linter Reference
ESLint eslint.md — plugin table, AST selectors, type-aware rules, auto-fix
Ruff ruff.md — 800+ reimplemented rules, selection, auto-fix, pyproject config
Pylint pylint.md — plugin table, astroid AST, type inference, custom checkers
RuboCop rubocop.md — gem table, node pattern DSL, auto-correct, custom cops
Stylelint stylelint.md — plugin table, PostCSS AST, custom rules, SCSS
Clippy clippy.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.