holohub-debug-build-run

Diagnose and minimally fix failing HoloHub CLI commands with reproducible verification.

3.2k|370|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/NVIDIA/skills --skill holohub-debug-build-run
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: holohub-debug-build-run
Source: https://github.com/NVIDIA/skills/tree/main/skills/holohub-debug-build-run
Command: npx skills add https://github.com/NVIDIA/skills --skill holohub-debug-build-run

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

When a concrete ./holohub command fails, hangs, regresses, or returns wrong output, this Skill turns that failure into a reproducible diagnosis, a minimal fix, and focused regression proof instead of guesswork or destructive trial-and-error.

Core Features & Use Cases

  • Structured Failure Reproduction: Freezes the exact command, revision, environment, and error boundary, then previews and reproduces the failure once without edits.
  • Layer-Based Diagnosis: Classifies failures across launcher, host, container, build, test, and application layers, testing one falsifiable hypothesis at a time.
  • Safe Minimal Fixes: Changes only the owning layer, keeps cache cleanup behind explicit user approval, and proves the fix with the identical command plus a focused regression test.
  • Use Case: A developer runs ./holohub run endoscopy_tool_tracking and it exits 1 with ModuleNotFoundError: holoscan; the Skill isolates whether the wrapper environment or the project container is at fault, applies the smallest fix, and verifies the identical command passes.

Quick Start

Ask your agent to diagnose why your exact failing ./holohub command fails and to fix it minimally with proof, for example: "./holohub build my_app fails after my dependency change, find the root cause and fix it."

Frequently Asked Questions about holohub-debug-build-run

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

FAQPage Schema
How do I debug a failing ./holohub command?

Provide the exact failing command, expected versus observed output, and your HoloHub checkout. The Skill freezes the reproduction, previews the identical command with dry-run flags, reproduces it once, isolates the failing layer, and applies a minimal fix with regression proof.

How do I diagnose a HoloHub build failure after changing dependencies?

The Skill captures the first causal CMake or compiler error rather than shutdown noise, then tests metadata, operator targets, and include/link paths as separate boundaries. It changes only the owning root cause and preserves your unrelated uncommitted edits.

Does this Skill handle HoloHub commands that hang instead of failing?

Yes. For hangs, it preserves all effect-bearing arguments but enforces an external timeout derived from the recorded hang boundary, then records the deadline, termination signal, exit status, and any remaining child processes.

Will the Skill clear HoloHub build caches during diagnosis?

Not without explicit approval. Cache cleanup is treated as a separate hypothesis: the Skill previews the narrowest clear-cache scope, shows every resolved path, and only proceeds after you authorize those exact paths.

When should I not use this HoloHub debug skill?

Do not use it for non-failing work. New application development routes to holohub-app-lifecycle, module packaging to holohub-module-lifecycle, and first-time SDK installation to holoscan-setup; the Skill never manufactures a failure to justify itself.

What HoloHub and Holoscan versions does the debugging guidance support?

The CLI contract and known-issues references were verified against holoscan-cli 4.5.0 and the HoloHub tag holoscan-sdk-4.5.0. Version-sensitive behavior is always rechecked against local help and the exact checkout before acting.