Run local CI validation using hyperi-ci before pushing code. Use when the user says /ci-check, asks to validate, or before any push.
This skill is ONLY for projects using hyperi-ci. Verify .hyperi-ci.yaml exists.
| Command | What it does | When to use |
|---|---|---|
hyperi-ci check | Quality + test | Default — always before push |
hyperi-ci check --quick | Quality only (lint, format, type check) | Fast WIP validation |
hyperi-ci check --full | Quality + test + build (native target) | Pre-release validation |
Default to unless the user specifies otherwise:
hyperi-ci checkhyperi-ci check
The output shows each stage (quality, test, optionally build) with pass/fail.
If everything passes: Report success, proceed with whatever the user was doing.
If quality fails:
cargo fmt, ruff format ., etc.)hyperi-ci check --quick to verify the fixIf tests fail:
hyperi-ci check (full, not quick)Do NOT proceed with git push if hyperi-ci check fails. Fix first.
The check command auto-detects the project language from .hyperi-ci.yaml.
| Language | Quality includes | Test includes |
|---|---|---|
| Rust | cargo fmt --check, cargo clippy, cargo audit | cargo nextest run or cargo test |
| Python | ruff check, ruff format --check, type checker, pip-audit, bandit | pytest with coverage |
| TypeScript | eslint, prettier --check, tsc --noEmit | vitest or jest |
| Go | golangci-lint, go vet, govulncheck | go test ./... |
All hyperi-ci projects also have Makefile targets:
make check # = hyperi-ci check
make quality # = hyperi-ci run quality
make test # = hyperi-ci run test
make build # = hyperi-ci run build