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.)
Resumen
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.
Archivos 7 archivos
Instálala a mano
Deska ejecuta esto por ti, para cada agente que elijas. Para ejecutarlo tú en una terminal:
npx skills add zernie/vigiles --skill linter-docsMás de zernie
- edit-speczernieEdit a vigiles .spec.ts to change a compiled instruction file (CLAUDE.md / AGENTS.md) — add, modify, or remove a rule, section, command, or key file. Use whenever you need to change a CLAUDE.md/AGENTS.md that carries a vigiles hash (edit the spec, never the artifact), including adding a new enforce()/check()/guidance() rule.2,000 instalaciones en skills.sh0
- strengthenzernieUpgrade a vigiles spec's guidance() rules to enforce() — scan the guidance rules in a CLAUDE.md/AGENTS.md spec and find existing linter rules (ESLint, Ruff, Clippy, Pylint, RuboCop, Stylelint) that back them. Use when asked to strengthen, harden, or make vigiles rules enforceable; NOT for general linting or fixing lint errors.2,000 instalaciones en skills.sh0
- test-harnesszernieInstall vigiles and test a Claude Code harness — hooks, skills, agents, settings, CLAUDE.md — by picking the right tier (unit / deterministic / eval) and writing a test that passes. Use to check that a hook fires or blocks, that a skill triggers, that injected context lands; or to observe a run — which tools it called, whether it stayed inside its declared allowed-tools, what files and side effects it produced, how to intercept a call without executing it.2,000 instalaciones en skills.sh0
- adopt-speczernieAdopt a typed .spec.ts for an existing hand-written CLAUDE.md — start from the file you already have, non-destructively1,800 instalaciones en skills.sh0
