Run any Skill in Manus with one click

spice-run

Stars86

Forks5

UpdatedMay 31, 2026 at 23:53

Compile and/or run a Spice program with the `spice` CLI — build to an executable, run a file directly, run with a sanitizer, run its enclosed tests, or cross-compile. Use when the user wants to execute a `.spice` file or produce a binary from one.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

spicelang

spicelang/spice

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	spice-run
description	Compile and/or run a Spice program with the `spice` CLI — build to an executable, run a file directly, run with a sanitizer, run its enclosed tests, or cross-compile. Use when the user wants to execute a `.spice` file or produce a binary from one.

Compile & run Spice programs

Uses the spice compiler at cmake-build-debug/src/spice (build it via the spice-build skill first).

SPICE=cmake-build-debug/src/spice

Subcommands

Command	Alias	Purpose
`spice build <file.spice>`	`b`	Compile to an output container (default: executable)
`spice run <file.spice>`	`r`	Compile and execute immediately
`spice test <file.spice>`	`t`	Compile with a test entry point and run enclosed tests
`spice install <file.spice>`	`i`	Build and install to a PATH dir
`spice uninstall <file.spice>`	`u`	Remove an installed program

Common usage

# Compile to a named executable
$SPICE build path/to/main.spice -o ./myprog
./myprog

# Compile + run in one step (best for quick checks)
$SPICE run path/to/main.spice

# Optimized build
$SPICE build -O2 path/to/main.spice -o ./myprog

# Run the program's own tests
$SPICE test path/to/main.spice

Useful options (build / run / test)

-o, --output <path> — output file path (build).
-O0..-O3, -Os, -Oz — optimization level; -lto enables LTO.
-m, --build-mode debug|release|test — build mode.
--sanitizer=address (and friends: TSAN, TYSAN, …) — run under a sanitizer, e.g. $SPICE run --sanitizer=address file.spice.
-b, --build-var key=value — parametrize the compiled program.
-j, --jobs <n> — parallel compile jobs.
--output-container exec|obj|lib|dylib — output format (build).
--static — link statically.
--no-entry — don't generate a main.
-d, --debug-output — verbose compiler debug output.
--ignore-cache — force full recompilation.

Cross-compiling

# By target triple
$SPICE build --target aarch64-linux-gnu path/to/main.spice -o ./myprog

# Or piecewise
$SPICE build --target-arch aarch64 --target-os linux path/to/main.spice -o ./myprog

Stable targets: linux/x86_64, linux/aarch64, windows/x86_64, darwin/aarch64, webassembly. Others (x86, armv7, riscv, mips, powerpc, nvptx, amdgpu, …) compile without stability guarantees.

To inspect the IR/assembly the compiler produces instead of running, use the spice-dump skill. Run $SPICE --help for the complete, current option list.

More from this repository

same repository

spice-build

spicelang/spice

Build the Spice compiler (`spice`) and/or the test runner (`spicetest`) with CMake/Ninja. Use when the user wants to compile/rebuild the project, build a specific target, produce a release/debug build, or set up the CMake build directory before running or testing.

2026-06-2486

spice-contribute

spicelang/spice

Guidelines for contributing changes to the Spice GitHub repository — branch naming conventions, commit message format, PR workflow, no-push-to-main rule, and quality gates. Use when preparing a branch for review, writing a commit, opening a PR, or checking that a contribution is ready to merge.

2026-06-0786

spice-profiling

spicelang/spice

Profile and benchmark the Spice compiler (the host C++ `spice` program) and the native binaries it emits from `.spice` files — using the built-in per-stage timers, the dedicated CMake profiling build options, and external tools (perf, valgrind/callgrind, flamegraph, hyperfine). Covers the preferred build/compile settings for representative profiling of each layer. Use when the user wants to find where compile time or runtime is spent, benchmark a change, or chase a performance regression.

2026-06-0186

spice-debugging

spicelang/spice

Find, diagnose, and fix bugs in the Spice compiler or in a compiled Spice program using GDB, objdump, sanitizers (for both the host C++ compiler and the emitted Spice program via the built-in `--sanitizer` flag), the compiler dump flags, and valgrind. Use when investigating a crash, miscompilation, memory error, or undefined behavior, or when triaging a failing test. Whenever a bug is fixed, this skill also requires extending or adding a test that covers the problematic code path and any related uncovered paths.

2026-06-0186

spice-add-test

spicelang/spice

Add a reference/integration test case under test/test-files for the Spice compiler. Covers the directory layout (flat vs grouped suites), the exact reference filenames the runner compares against, control/skip marker files, platform-specific variants, and the --update-refs workflow to generate expected output. Use when adding or modifying compiler test cases.

2026-06-0186

spice-architecture

spicelang/spice

Orientation map of the Spice compiler codebase — the compilation pipeline (lexer → parser → CST → AST → import collector → symbol table → type checker → IR generator → optimizer → object emitter → linker), the key class/file for each stage, and the SourceFile orchestration sequence. Use when navigating the compiler, deciding where a change belongs, or understanding how a stage feeds the next.

2026-06-0186

name	spice-run
description	Compile and/or run a Spice program with the `spice` CLI — build to an executable, run a file directly, run with a sanitizer, run its enclosed tests, or cross-compile. Use when the user wants to execute a `.spice` file or produce a binary from one.

Compile & run Spice programs

Uses the spice compiler at cmake-build-debug/src/spice (build it via the spice-build skill first).

SPICE=cmake-build-debug/src/spice

Subcommands

Command	Alias	Purpose
`spice build <file.spice>`	`b`	Compile to an output container (default: executable)
`spice run <file.spice>`	`r`	Compile and execute immediately
`spice test <file.spice>`	`t`	Compile with a test entry point and run enclosed tests
`spice install <file.spice>`	`i`	Build and install to a PATH dir
`spice uninstall <file.spice>`	`u`	Remove an installed program

Common usage

# Compile to a named executable
$SPICE build path/to/main.spice -o ./myprog
./myprog

# Compile + run in one step (best for quick checks)
$SPICE run path/to/main.spice

# Optimized build
$SPICE build -O2 path/to/main.spice -o ./myprog

# Run the program's own tests
$SPICE test path/to/main.spice

Useful options (build / run / test)

-o, --output <path> — output file path (build).
-O0..-O3, -Os, -Oz — optimization level; -lto enables LTO.
-m, --build-mode debug|release|test — build mode.
--sanitizer=address (and friends: TSAN, TYSAN, …) — run under a sanitizer, e.g. $SPICE run --sanitizer=address file.spice.
-b, --build-var key=value — parametrize the compiled program.
-j, --jobs <n> — parallel compile jobs.
--output-container exec|obj|lib|dylib — output format (build).
--static — link statically.
--no-entry — don't generate a main.
-d, --debug-output — verbose compiler debug output.
--ignore-cache — force full recompilation.

Cross-compiling

# By target triple
$SPICE build --target aarch64-linux-gnu path/to/main.spice -o ./myprog

# Or piecewise
$SPICE build --target-arch aarch64 --target-os linux path/to/main.spice -o ./myprog

To inspect the IR/assembly the compiler produces instead of running, use the spice-dump skill. Run $SPICE --help for the complete, current option list.