rebuild-all-test-components

Rebuilds the complete Golem test-component WASM artifact set via cargo make.

1.5k|212|Updated Nov 24, 2023
One-click install
npx skills add https://github.com/golemcloud/golem --skill rebuild-all-test-components
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rebuild-all-test-components
Source: https://github.com/golemcloud/golem/tree/main/.agents/skills/rebuild-all-test-components
Command: npx skills add https://github.com/golemcloud/golem --skill rebuild-all-test-components

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Golem's worker and integration tests depend on dozens of prebuilt WebAssembly test components across Rust, TypeScript, and benchmark suites. When many of these WASMs are missing or stale, developers need a single authoritative rebuild path instead of manually compiling each component.

Core Features & Use Cases

  • Full artifact rebuild: Runs cargo make build-test-components, which builds prerequisites including golem-cli and the TypeScript SDK, then rebuilds all Rust, TypeScript, and benchmark test components.
  • Migration preservation: Detects and keeps automatic source migrations that the latest Golem binary applies to component manifests and embedded skills during the rebuild.
  • Scoped alternatives: Supports focused rebuilds via build-components.sh rust, ts, benchmarks, or chunk groups like rust-N, plus dedicated tasks for the two excluded component-model-async fixtures.
  • Use Case: After updating the TypeScript SDK, a developer cleans the SDK dist, runs the full rebuild, validates the produced WASMs with wasm-tools, and commits both the artifacts and any automatic migrations.

Quick Start

Ask the agent to run a full rebuild of all Golem test components from the repository root and validate the resulting WASM artifacts.

Frequently Asked Questions about rebuild-all-test-components

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I rebuild all Golem test components?

Run cargo make build-test-components from the repository root. It builds prerequisites including golem-cli and the TypeScript SDK, then runs test-components/build-components.sh rebuild across the Rust, TypeScript, and benchmark component arrays.

How do I rebuild only some Golem test components?

Use ./build-components.sh with a scope argument such as rust, ts, benchmarks, or a chunk like rust-N or ts-N. Run ./build-components.sh list-groups to see the CI matrix groups, and use the modifying-test-components skill for a single component.

Why does the TypeScript SDK not rebuild during build-test-components?

The build-sdk-ts step skips work if both the SDK dist directory and wasm/agent_guest.wasm already exist, which does not prove freshness. After TS SDK changes, clean and rebuild the SDK and agent template before running the full rebuild.

Which test components are excluded from the full rebuild?

Two minimal component-model-async fixtures are excluded: build-concurrent-delivery-order-component and build-concurrent-runtime-events-component. Run those dedicated cargo make tasks only when their sources or committed WASMs must change.

Should I revert source changes that appear after rebuilding test components?

No. The latest Golem binary may automatically migrate component manifests, embedded skills, or other metadata during the rebuild. Confirm the changes came from the rebuild, then keep and include every migration in the changeset.