ci
/ci
Run Vale in GitHub Actions, a pre-commit hook, or another runner. Use when the user says "add vale to CI", "run vale on PRs", "add a pre-commit hook", or "make the build fail on style errors".
- Author
- vale-cli ↗
- Repository
- agent-tools ↗
- Licence
- MIT
- Last repository change
- 02.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 02.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Run Vale in GitHub Actions, a pre-commit hook, or another runner. Use when the user says "add vale to CI", "run vale on PRs", "add a pre-commit hook", or "make the build fail on style errors".
Triggers from the description
Original author description
Run Vale in GitHub Actions, a pre-commit hook, or another runner. Use when the user says "add vale to CI", "run vale on PRs", "add a pre-commit hook", or "make the build fail on style errors".
How it works
- When to use this
- Prerequisites
- Advisory or blocking
- GitHub Actions
- pre-commit
- Any other runner
- Do not
SKILL.md preview
---
name: ci
description: Run Vale in GitHub Actions, a pre-commit hook, or another runner. Use when the user says "add vale to CI", "run vale on PRs", "add a pre-commit hook", or "make the build fail on style errors".
---
# Put Vale in the pipeline
## When to use this
Vale runs locally and should now run automatically.
## Prerequisites
1. `vale ls-config` resolves, and a plain `vale <path>` run works locally. Do
not wire up CI for a config that does not resolve — the failure will look
like a CI problem.
2. The user has said whether the job should block. Ask if not.
## Advisory or blocking
**Only `error` sets a non-zero exit code.** Warnings and suggestions exit 0, so
a job wired up naively passes no matter how much it reports.
- **Advisory** — Vale reports, the job stays green. The right way to adopt Vale
on a corpus that has never had it.
- **Blocking** — the rules the team cares about are set to `error` in the
config, and the job fails on those.
Say which one you are setting up, in those words. "It runs in CI" tells nobody
whether it can stop a merge.
## GitHub Actions
```yaml
- uses: vale-cli/vale-action@reviewdog
with:
files: docs
```
Alerts arrive as review comments on the pull request, which is where a writer
will see them.
## pre-commit
```yaml
repos:
- repo: https://github.com/vale-cli/vale
rev: v3.17.0
hooks:
- id: vale
```
Pin `rev` to a release. Hooks that float break at the worst time.
## Any other runner
```bash
vale --no-global --output=line docs/
```
`--output=line` gives `path:line:col:rule:message`, which most CI systems can
turn into annotations. `--no-global` keeps a config on the machine from
changing the result.
If the runner has no cached `StylesPath`, `vale sync` has to run first — and
that means a style updating upstream can fail a build nobody changed. Pin
`Packages` to a release URL rather than a moving reference.
## Do not
- **Do not add `--no-exit` to make a failing job pass.** If those alerts should
not block, change the levels in the config, where the decision is visible to
the team.
- **Do not raise `MinAlertLevel` in CI only.** A config that reports different
things locally and in CI is how people stop trusting the tool.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · vale-cli/agent-tools | 100 | MIT |
| A7-studio/jobmigo | 100 | MIT |
| gagarin-cloud/plugin | 100 | MIT |
| andriiklymiuk/corgi | 100 | MIT |
| kamoca-labs/docker | 100 | MIT |
| pawangai/pawang-agents | 100 | MIT |
| agentic-dev3o/devx-plugins | 100 | MIT |
| chachamaru127/claude-code-harness | 100 | MIT |
| onsi/ginkgo | 100 | MIT |
Database snapshot: 13.11.2026 · package version bb701a16ce00 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100setup
Install Vale, write a .vale.ini, sync styles, and get a first run. Use when the user says "set up vale", "add vale", "add prose linting", or "lint our docs" in a repository that has no Vale config yet. - 100fix
Run Vale, fix error-level alerts, and open a pull request per file. Use when the user says "run vale", "fix vale errors", "lint the docs", "fix the linter", or "make vale pass". Fixes errors only; leaves warnings and suggestions for a person. - 100vale
Run Vale prose linter and auto-fix issues. Use when linting or proofreading markdown/text. - 100vale
Install, repair, and validate Vale prose linting. Use when users need Vale config, style sync, docs lint gates, or broken Vale workflow diagnosis. - 100pre-commit-hook-setup
Configure pre commit hook setup operations. Auto-activating skill for DevOps Basics. Triggers on: pre commit hook setup, pre commit hook setup Part of the DevOps Basics skill category. Use when working with pre commit hook setup functionality. Trigger with phrases like "pre… - 100sc-git
GitHub repo CRUD + Actions cost reduction. Audit workflow burn rate, disable noisy YAML (workflow_dispatch-only with backup), run CI locally instead of cloud minutes, install pre-push hook, install self-hosted runner at VPS, POST commit statuses, register VPS crontab. Replaces…