sd-prose-lint

Lint prose with Vale gates and disposition every finding before commit or send.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/platypeeps/sd-ai-command-pack --skill sd-prose-lint-platypeeps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sd-prose-lint
Source: https://github.com/platypeeps/sd-ai-command-pack/tree/main/skills/sd-prose-lint
Command: npx skills add https://github.com/platypeeps/sd-ai-command-pack --skill sd-prose-lint-platypeeps

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Prose written on your behalf — skill bodies, docs, commit messages, PR text, release notes, outbound drafts — often ships with style violations and AI tells that a deterministic gate would have caught. This Skill runs the Vale prose gate where it exists, degrades gracefully where it does not, and assigns every finding a disposition instead of silently rewriting your text. ## Core Features & Use Cases - Deterministic gate detection: Probes for a make prose-lint target or local Vale binary, classifies the gate state (full gate, binary only, target only, absent), and reports gaps plainly without blocking the session. - Finding dispositions: Every error-level finding gets exactly one disposition — fix, suppress with recorded justification, or promote as a config proposal to the gate owner. - Judgment pass and optional scoring: Reads prose for tells no rule covers (hedging stacks, filler, formulaic transitions), and optionally scores dimensions via jev when explicitly requested and the draft is not confidential. - Use Case: Before merging a PR, run the lint over changed Markdown files; receive a report listing each Vale finding with its disposition, judgment-pass tells, and rewrite-shaped findings handed back to the prose owner. ## Quick Start Run a prose lint over the changed files in my working tree and report each finding with its disposition.

Frequently Asked Questions about sd-prose-lint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I lint prose with Vale before committing?▼

Run the prose lint over changed files in your working tree. It probes for a make prose-lint target or local Vale binary, runs the deterministic pass, and reports each finding by file, line, rule, and severity with a disposition.

What happens when Vale is not installed in a repository?▼

The lint degrades gracefully: it reports the missing gate in one plain sentence, naming whether the repository has no gate or the environment cannot run it, then continues with the judgment pass. It never fails or blocks the session over a missing gate.

Does the prose lint rewrite flagged text automatically?▼

No, it reports and dispositions findings but never rewrites. Mechanical corrections are marked as fixes, while anything requiring re-composed sentences is handed back to the prose owner with the finding list attached.

Can I get numeric prose quality scores from a lint run?▼

Yes, but only when you explicitly ask for scores and jev is enabled in the environment. The scoring step reads the dimensions reference, reports raw scores and confidence per dimension, and is skipped entirely for confidential drafts.

When should I not use a prose lint?▼

Skip it for rewriting flagged prose into human-sounding text, full editorial review of technical drafts, and linting code, schemas, or configuration. Those belong to a technical editor or the prose owner, not the lint gate.