prose-lintlisted
Install: claude install-skill tomkd555/prose-lint
# Prose lint
Runs the linters over one text on demand, settles which config the text's
language calls for, and rules on every hit. Read `{SKILL_DIR}` below as the
absolute path of this skill's directory, and `{HOME}` as `$PROSE_LINT_HOME`, or
`~/.prose-lint` when that is unset.
## Step 0 - setup
The plugin's SessionStart hook sets up the linters in the background, on the
first session after an install or an update. It fetches uv when none is on
PATH and runs `scripts/setup.py`, which copies the textlint and vale configs
and the registers to `{HOME}`, downloads vale and Node with npm under `{HOME}`
when they are not on PATH, and runs `npm install` and `vale sync`.
`{HOME}/.setup-version` names the plugin version of the last setup that
finished. When it is missing or older than this plugin, as after an install
in the running session, run the hook's script and wait for it:
```
bash {SKILL_DIR}/../../hooks/session-start.sh
```
It prints the log's path and every `skip` or `fail` line. The plugin's other
hooks (`hooks/lint.py`) run textlint and the register on each file Claude
writes, on each Japanese reply, and on plans and questions before they reach
the user; this skill runs every layer. A skill copied by
hand has no hook; run `uv run python {SKILL_DIR}/scripts/setup.py` there. A
layer whose tool is still missing is reported as skipped in the final report;
the other layers still run.
The commands below start with `prose-lint-run`, which the plugin puts on PATH:
it adds the