Linter Docs

zernie/vigiles/skills/linter-docs

by zernie1d562c69566fNo license15 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

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

Instructions only

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 [blocked] — plugin table, AST selectors, type-aware rules, auto-fix
Ruffruff.md [blocked] — 800+ reimplemented rules, selection, auto-fix, pyproject config
Pylintpylint.md [blocked] — plugin table, astroid AST, type inference, custom checkers
RuboCoprubocop.md [blocked] — gem table, node pattern DSL, auto-correct, custom cops
Stylelintstylelint.md [blocked] — plugin table, PostCSS AST, custom rules, SCSS
Clippyclippy.md [blocked] — 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.

Source and attribution

Source:zernie/vigilesinskills/linter-docsat commit1d562c6

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from zernie/vigiles

Debug My Harness

zernie

Diagnoses agent harness misbehavior by reading the local .vigiles/runs.jsonl flight-recorder ledger.

AI & Agents15updated today

Review Docs

zernie

Review the README or a documentation page from several real reader points of view at once. Fans out one parallel reviewer per audience — Claude Code newcomer, power user, plugin/skill author, skeptical senior engineer, non-running decision-maker — each scoring it x/5 and naming concrete, line-level fixes. Use when asked to review, critique, grade, or "get to N/5" the README or any front-door doc, or to check how a doc reads for real users. Not for code review (use /code-review for that).

Awaiting classification15updated today

Adopt Spec

zernie

Converts an existing hand-written CLAUDE.md into a typed CLAUDE.md.spec.ts using the vigiles spec library.

AI & Agents15updated today

Pr To Lint Rule

zernie

Turns a recurring prose code-review rule into a custom lint rule, gated by an independent soundness test that abstains if it leaks.

Software Development15updated today

Enforce Rules Format

zernie

Validates that project instruction-file rules carry proper enforcement classifications and fixes missing ones.

AI & Agents15updated today

Deep Research

zernie

Use when the user asks to research a topic in depth, map a competitive/market landscape, run a multi-source investigation, or "fan out" parallel research agents — anything where many findings must be gathered and then NOT lost. Enforces durable, detail-preserving research (write full findings to disk; keep a full appendix beside the synthesis).

Awaiting classification15updated today