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.