golem-troubleshoot-build

Isolate Golem build pipeline steps and validate golem.yaml manifest configurations.

Updated May 17, 2026
One-click install
npx skills add https://github.com/Rust-soham/golem-claw --skill golem-troubleshoot-build-rust-soham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golem-troubleshoot-build
Source: https://github.com/Rust-soham/golem-claw/tree/main/packages/golem/.agents/skills/golem-troubleshoot-build
Command: npx skills add https://github.com/Rust-soham/golem-claw --skill golem-troubleshoot-build-rust-soham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you diagnose why a Golem build fails or why your golem.yaml configuration values aren’t being applied as expected at build time or runtime.

Core Features & Use Cases

  • Build-step isolation: Run the build pipeline in single-step mode to quickly pinpoint whether failures come from tool checks, compilation, metadata embedding, or bridge generation.
  • Dependency and feature validation: Identify missing Rust/TypeScript dependencies or incompatible versions and understand what the CLI expects to find or auto-fix.
  • Manifest debugging with trace: Use manifest-trace output to see the exact layer responsible for each resolved property value, merge behavior, and environment-specific preset selection.
  • Practical examples for common issues: Target frequent problems like missing tools, wrong Rust targets, stale dependency features, decorator/tsconfig mismatches, and incorrect environment overlays.

Quick Start

Run golem build --step check --yes to detect the failing build stage and surface actionable install or fix guidance.

Frequently Asked Questions about golem-troubleshoot-build

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

FAQPage Schema
How do I troubleshoot a Golem build failure and isolate the failing pipeline step?

To troubleshoot a Golem build failure, run the build pipeline in single-step mode using golem build --step check --yes to isolate whether failures originate from tool checks, compilation, metadata embedding, or bridge generation.

Why are my golem.yaml configuration values not applying as expected at build time?

Your golem.yaml configuration values may not apply due to incorrect environment overlays or merge behavior; use golem component manifest-trace to see the exact layer responsible for each resolved property value.

Does Golem build troubleshooting support Rust wasm32-wasip2 targets and TypeScript tsconfig projects?

Yes, Golem build troubleshooting supports Rust wasm32-wasip2 targets and TypeScript tsconfig projects by validating required tools, dependencies, and feature compatibility during build-step isolation.

What is the best way to debug missing dependencies when a Golem component build fails?

The best way to debug missing dependencies in a failed Golem component build is to run dependency and feature validation checks to identify missing Rust or TypeScript packages and incompatible versions.

How does golem component manifest-trace work for resolving environment-specific presets?

Golem component manifest-trace outputs the exact layer responsible for each resolved property value, showing merge behavior, appliedLayers, per-property origins, and environment-specific preset selection.

What should I do when Golem build step checks fail due to missing tools or wrong Rust targets?

When Golem build step checks fail due to missing tools or wrong Rust targets, the single-step isolation mode surfaces actionable install or fix guidance to resolve the detected build stage failures.