Vale Review
Run the Vale prose linter as an independent, deterministic reviewer for a @swamp/software-factory writing-review stage. Emits Vale's alerts in the same kind: findings contract a judgement-based LLM reviewer produces, so both plug into the factory's findings-clear gate identically.
Severity maps Vale error → high, warning → medium, suggestion → low, so a gate blocking on [critical, high] blocks on Vale errors while recording the softer alerts non-blockingly. The first finding is always a VALE-0 recon entry, so a clean pass states what ran rather than returning an empty array.
The extension ships NO styles and NO .vale.ini: it provides the capability,
and the style guide is the caller's private configuration. Point it at your
own config with the configPath global argument; Vale resolves StylesPath
relative to that file. A missing Vale binary yields valeAvailable: false
rather than a thrown error, and Vale exit code 1 (issues found) is treated as
a normal result.
Use
swamp extension pull @atalanta/vale-review
swamp model create @atalanta/vale-review my-vale
swamp model edit my-vale # set configPath to your repo's .vale.ini
swamp model method run my-vale review --input path=doc.mdGlobal Arguments
| Argument | Type | Description |
|---|---|---|
| valePath | string | Path or command name for the Vale binary. |
| configPath | string | Path to the caller's Vale config. Vale resolves StylesPath relative to |
| wallTimeoutMs | number | Hard ceiling for a single Vale invocation. |
| Argument | Type | Description |
|---|---|---|
| path | string | Path to the file Vale should lint. |
Resources
- Has README or module doc2/2earned
- README has a code example1/1earned
- README is substantive1/1earned
- Most symbols documented1/1earned
- No slow types (deprecated)1/1earned
- Dependencies pass trust audit2/2earned
- Has description1/1earned
- Platform support declared (or universal)2/2earned
- License declared1/1earned
- Verified public repository0/2missing