.github/skills/ci-cd-pipeline/SKILL.md
Guide for Nanvix CI and GitHub Actions workflow behavior, including local pipeline execution and matrix coverage. Use this when asked about CI checks, workflow failures, or release flow.
npx skillsauth add nanvix/nanvix ci-cd-pipelineInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill when the user asks about the continuous integration and deployment pipeline, GitHub Actions workflows, or automated quality checks.
./scripts/pipeline.sh
The pipeline runs all quality checks and tests across the supported configuration matrix.
The pipeline runs these steps in order:
spellcheck and format run once (not per-machine).scripts/pipeline.sh executes machine-dependent
steps for microvm and hyperlight.
| Machine | Build Types | Deployment Types |
|---------------|----------------|-------------------------------|
| microvm | debug, release | standalone, single, multi, l2 |
| hyperlight | debug, release | single, multi, l2 |
| Deployment Type | DEPLOYMENT_MODE |
|-----------------|-------------------|
| standalone | standalone |
| single-process | single-process |
| multi-process | multi-process |
| l2 | l2 |
# Spell check.
./z build -- spellcheck
# Format check.
./z build -- format-check
# Lint check.
./z build -- lint-check
# Formal verification.
./z build -- verify
# Unit tests.
./z build -- run-unit-tests
Workflows are defined in .github/workflows/. They follow the same quality gates as the local
pipeline, but matrix coverage is split across multiple jobs (including dedicated L2 jobs) and run on
pull requests and pushes to dev.
Matrix coverage in GitHub Actions:
checks: format + spellcheck (single run).lint, verify, ci-build: microvm and hyperlight with standalone,
single-process, and multi-process.ci-test: same matrix, excluding hyperlight + standalone.ci-l2: separate L2 jobs for microvm and hyperlight.Note: The
ci-windowsworkflow validates Windows host builds (nanvixd, UserVM, source checks) and runs a smoke test using nanvixd in standalone interactive mode on WHP-enabled runners.
# Create a release archive.
./z build -- release
# The archive name follows this pattern:
# nanvix-<ver>-<target>-<machine>-<deploy>-<mode>-<log>-<memory>mb.tar.bz2
Minor releases can be created with:
./scripts/create-minor-release.sh
The pipeline tracks and reports:
development
Guide for developing, building, and running Nanvix user-space applications across supported runtimes and languages. Use this when asked about guest app implementation or execution.
development
Guide for diagnosing Nanvix build, runtime, and test failures, including cleanup and debugging workflows. Use this when asked to investigate errors or unstable behavior.
testing
Guide for running Nanvix tests with z. Use this when asked to run unit tests, integration tests, or the full test suite.
development
Guide for writing, running, and debugging Nanvix unit, integration, and system tests in Rust and C/C++. Use this when asked about test implementation or failures.