Prioritise Vale alerts with AI
Turn a noisy first lint run into a short list of editorial decisions. See which rules dominate and which issues can actually block a build.
Prioritise Vale alerts with AI after switching on a style guide for a long-running documentation collection. The triage skill groups findings by the rule that produced them. Fifty pages can look noisy for exactly the same reason; an editor can settle that question once instead of debating every occurrence separately.
The report distinguishes the amount of work from the severity assigned to it. A frequent suggestion may require an editorial decision but cannot stop a build on its own. A small group of errors may be easy to clear first. When a rule genuinely conflicts with house style, record the reason for changing it.
What it does
- Count hits by rule across the collection and retain their severity.
- Identify the few rules that dominate the first report.
- Recommend a fix for a small, clear group of genuine issues.
- Downgrade a sound rule when the backlog makes immediate enforcement impractical.
- Explain any proposed removal in terms of a specific house-style choice.
Install and use
- Install the skill with Vale, its project styles and jq available. Choose the prose collection you want to review.
- Ask “Group the first run by rule and explain which changes would affect what our writers are expected to do.”
- Review the proposed decisions with the editor before changing the rules or the documents.
FAQ
Source
Made by Joseph Kato (Vale). Original skill: triage, published on GitHub under the MIT licence.
View on GitHub