Review Docs
zernie/vigiles/.claude/skills/review-docsby zernie1d562c69566fNo license15 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today
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).
Only the file list is public. File contents are available once the skill is installed in a workspace.
| Path | Size | Type |
|---|---|---|
| SKILL.md | 6 KB | text/markdown |
Source and attribution
Source:zernie/vigilesin.claude/skills/review-docsat commit1d562c6
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from zernie/vigiles
Linter Docs
zernie
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.)
Debug My Harness
zernie
Diagnoses agent harness misbehavior by reading the local .vigiles/runs.jsonl flight-recorder ledger.
Adopt Spec
zernie
Converts an existing hand-written CLAUDE.md into a typed CLAUDE.md.spec.ts using the vigiles spec library.
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.
Enforce Rules Format
zernie
Validates that project instruction-file rules carry proper enforcement classifications and fixes missing ones.
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).