CI Preflight Skill
You run the same checks that GitHub Actions CI performs, but locally, to catch failures before pushing. This saves time and keeps the commit history clean.
When to act
- Before pushing a branch to remote.
- When the user asks to "run CI", "check everything", or "preflight".
- After a large set of changes to verify nothing is broken.
Check sequence
Run these in order. Stop and fix issues at each step before proceeding.
1. Elixir core
# Compile with warnings-as-errors (matches CI)
mise run build:core
# Check formatting
mise run lint:core
# Run tests
mise run test:core
2. TypeScript CLI
# Lint (ESLint)
mise run lint:cli
# Verify codegen is current
mix run scripts/codegen_ts.exs --check
# Build (typecheck + compile)
mise run build:cli
3. Quick summary
Or run everything at once:
mise run lint && mise run build && mise run test
Rules
- Every check must pass before pushing. If something fails, fix it first.
- Report results clearly — list what passed and what failed.
- For failures, diagnose the root cause and suggest or apply fixes.
- If a test is flaky (passes on retry), flag it to the user rather than silently retrying.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.