Run any Skill in Manus with one click

build

Stars3

Forks0

UpdatedApril 19, 2026 at 20:54

Clean-build the veb-in-c library and run all CTest suites (UnitTests + SortingBenchmark). Use after edits to vebtrees.h or anything under test/, or when the user wants to verify the build is green.

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

Bonifatius94

Bonifatius94/veb-in-c

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	build
description	Clean-build the veb-in-c library and run all CTest suites (UnitTests + SortingBenchmark). Use after edits to vebtrees.h or anything under test/, or when the user wants to verify the build is green.

/build

Runs the same ./build.sh script that CI runs. It wipes build/, reconfigures CMake in Release mode, builds, and runs CTest with CTEST_OUTPUT_ON_FAILURE=1.

Steps

From the repo root, run ./build.sh.
If CMake/GCC isn't installed, point the user at the README's apt line (sudo apt-get install -y build-essential cmake git).

Report

Whether configure, build, and tests each succeeded.
Which CTest targets ran (UnitTests, SortingBenchmark) and their status.
On failure, surface the relevant compiler error or the failing test's output. Do not dump the full log.
On success, a one-line confirmation is enough — the user doesn't need the full build log.

Variants

Debug build: uncomment set(CMAKE_BUILD_TYPE Debug) in the top-level CMakeLists.txt, or pass -DCMAKE_BUILD_TYPE=Debug to cmake. Ask before switching — Release is the default and what CI checks.
Incremental build: if build/ already exists and the user is iterating, cmake --build build && ctest --test-dir build --output-on-failure is faster than a full clean. Still, clarify before skipping the clean step.

More from this repository

same repository

theory

Bonifatius94/veb-in-c

Theoretical background for veb-in-c's design choices — memeff root, bitwise leaves, the O(u)-bits derivation from issue

2026-05-033

refine

Bonifatius94/veb-in-c

Turn a GitHub issue into a concrete implementation plan for the veb-in-c codebase. Given an issue number, fetch the issue, map it onto the current code, and produce a step-by-step plan with affected files, invariants to preserve, and tests to add. Use when the user wants to start work on a tracked item from ROADMAP.md or the issue tracker.

2026-04-193

implement

Bonifatius94/veb-in-c

Pick up a refined GitHub issue and implement it end-to-end using strict red-green-refactor TDD. Creates a branch, cycles through Red/Green/Refactor with one commit per phase, and stops at a green local build. Use when the user hands you a ticket number that has already been through /refine.

2026-04-193

bench

Bonifatius94/veb-in-c

Run the SortingBenchmark and report the vEB-sort vs qsort timing comparison. Use when the user wants a perf number after changes to vebtrees.h.

2026-04-193

docs

Bonifatius94/veb-in-c

Generate the Doxygen documentation website for veb-in-c and report where the output zip landed. Use when the user wants to refresh docs after public-API or comment changes.

2026-04-193

Bonifatius94/veb-in-c

Generate a self-contained handoff prompt for the next Claude session to continue this session's work. Captures issue context, branch state, what's done, what's left, and gotchas. The user copies the output and pastes it as the opening prompt of the next session. Use at the end of a work session — especially when stopping mid-task.

2026-04-193

name	build
description	Clean-build the veb-in-c library and run all CTest suites (UnitTests + SortingBenchmark). Use after edits to vebtrees.h or anything under test/, or when the user wants to verify the build is green.

/build

Runs the same ./build.sh script that CI runs. It wipes build/, reconfigures CMake in Release mode, builds, and runs CTest with CTEST_OUTPUT_ON_FAILURE=1.

Steps

From the repo root, run ./build.sh.
If CMake/GCC isn't installed, point the user at the README's apt line (sudo apt-get install -y build-essential cmake git).

Report

Whether configure, build, and tests each succeeded.
Which CTest targets ran (UnitTests, SortingBenchmark) and their status.
On failure, surface the relevant compiler error or the failing test's output. Do not dump the full log.
On success, a one-line confirmation is enough — the user doesn't need the full build log.

Variants

Debug build: uncomment set(CMAKE_BUILD_TYPE Debug) in the top-level CMakeLists.txt, or pass -DCMAKE_BUILD_TYPE=Debug to cmake. Ask before switching — Release is the default and what CI checks.
Incremental build: if build/ already exists and the user is iterating, cmake --build build && ctest --test-dir build --output-on-failure is faster than a full clean. Still, clarify before skipping the clean step.