golem-troubleshoot-build

Diagnose Golem build failures and manifest configuration issues with trace outputs.

1|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/justcoon/golem-shopping-ts --skill golem-troubleshoot-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golem-troubleshoot-build
Source: https://github.com/justcoon/golem-shopping-ts/tree/main/.agents/skills/golem-troubleshoot-build
Command: npx skills add https://github.com/justcoon/golem-shopping-ts --skill golem-troubleshoot-build

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill assists developers in troubleshooting build failures and misconfigurations related to Golem's manifest files and build pipeline.

Core Features & Use Cases

  • Build Failure Diagnosis: Guides users through identifying issues during each pipeline step of golem build.
  • Manifest Inspection: Provides detailed tracing of configuration resolution via manifest-trace to pinpoint environment and layer conflicts.
  • Use Case: A developer encounters build errors or unexpected environment variable values; this Skill helps interpret logs and trace configuration layers to resolve them quickly.

Quick Start

Use the golem troubleshoot skill to analyze why your Golem build is failing or misconfigured.

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 during the pipeline execution?

Troubleshooting Golem build failures involves analyzing each pipeline step of `golem build` to identify execution errors, then applying targeted configuration fixes to ensure correct build pipeline execution and environment setup.

How does Golem manifest layering work when resolving environment variables?

Golem manifest layering resolves environment variables by stacking configuration layers, which can sometimes cause unexpected value conflicts or overrides during the build process if not traced correctly.

What is the best way to trace Golem manifest configuration conflicts?

The best way to trace Golem manifest configuration conflicts is by generating a `manifest-trace` output, which provides detailed tracking of configuration resolution to pinpoint exact environment and layer conflicts.

Do I need to know Golem CLI commands to diagnose manifest configuration issues?

Yes, diagnosing Golem manifest configuration issues requires understanding Golem CLI commands and manifest layering behaviors to interpret trace outputs and apply the correct environment setup fixes.

Why does my Golem build output unexpected environment variable values?

Unexpected environment variable values during a Golem build result from manifest layer conflicts or misconfigurations, requiring detailed configuration inspection via `manifest-trace` to pinpoint and resolve the exact layer conflicts.