How do I install the CI CD Pipeline skill?

Run npx skillmds@latest add tomevault-io/ci-cd-pipeline in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is CI CD Pipeline safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with CI CD Pipeline?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is CI CD Pipeline free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published CI CD Pipeline?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

CI CD Pipeline by tomevault-io — Agent Skill

Name: CI CD Pipeline
Author: tomevault-io

CI CD Pipeline

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. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

CI/CD Pipeline

Use this skill when the user asks about the continuous integration and deployment pipeline, GitHub Actions workflows, or automated quality checks.

Running the Full Pipeline Locally

./scripts/pipeline.sh

The pipeline runs all quality checks and tests across the supported configuration matrix.

Pipeline Steps

The pipeline runs these steps in order:

Spell Check — Checks spelling in source code.
Format Check — Verifies code formatting.
Lint Check — Runs Clippy and other linters.
Verify — Runs Verus formal verification on annotated crates.
Build — Compiles all targets.
Test — Runs unit and system integration tests.

Configuration Matrix

Machine-Independent Steps

spellcheck and format run once (not per-machine).

Machine-Dependent Steps

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

Build Parameter Mapping

Deployment Type	`DEPLOYMENT_MODE`
standalone	`standalone`
single-process	`single-process`
multi-process	`multi-process`
l2	`l2`

Individual Quality Checks

# 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

GitHub Actions Workflows

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-windows workflow validates Windows host builds (nanvixd, UserVM, source checks) and runs a smoke test using nanvixd in standalone interactive mode on WHP-enabled runners.

Release Process

# 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

Pipeline Output

The pipeline tracks and reports:

Pass/fail/skip counts per step.
Total elapsed time.
Detailed error output for failed steps.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: ci-cd-pipelinedescription: 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. Use when this capability is needed.---# CI/CD PipelineUse this skill when the user asks about the continuous integration and deployment pipeline, GitHubActions workflows, or automated quality checks.## Running the Full Pipeline Locally```bash./scripts/pipeline.sh```The pipeline runs all quality checks and tests across the supported configuration matrix.## Pipeline StepsThe pipeline runs these steps in order:1. **Spell Check** — Checks spelling in source code.2. **Format Check** — Verifies code formatting.3. **Lint Check** — Runs Clippy and other linters.4. **Verify** — Runs Verus formal verification on annotated crates.5. **Build** — Compiles all targets.6. **Test** — Runs unit and system integration tests.## Configuration Matrix### Machine-Independent Steps- `spellcheck` and `format` run once (not per-machine).### Machine-Dependent Steps`scripts/pipeline.sh` executes machine-dependentsteps for `microvm` and `hyperlight`.| Machine | Build Types | Deployment Types ||---------------|----------------|-------------------------------|| `microvm` | debug, release | standalone, single, multi, l2 || `hyperlight` | debug, release | single, multi, l2 |### Build Parameter Mapping| Deployment Type | `DEPLOYMENT_MODE` ||-----------------|-------------------|| standalone | `standalone` || single-process | `single-process` || multi-process | `multi-process` || l2 | `l2` |## Individual Quality Checks```bash# 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```## GitHub Actions WorkflowsWorkflows are defined in `.github/workflows/`. They follow the same quality gates as the localpipeline, but matrix coverage is split across multiple jobs (including dedicated L2 jobs) and run onpull 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-windows` workflow validates Windows host builds (nanvixd, UserVM, source checks)> and runs a smoke test using nanvixd in standalone interactive mode on WHP-enabled runners.## Release Process```bash# 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:```bash./scripts/create-minor-release.sh```## Pipeline OutputThe pipeline tracks and reports:- Pass/fail/skip counts per step.- Total elapsed time.- Detailed error output for failed steps.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/nanvix) — claim your Tome and manage your conversions.

Frequently asked questions