메뉴
Use when a concrete ./holohub command fails, hangs, regresses, or returns wrong output and needs reproducible diagnosis and verification.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/NVIDIA/skills --skill holohub-debug-build-run명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | holohub-debug-build-run |
| description | Use when a concrete ./holohub command fails, hangs, regresses, or returns wrong output and needs reproducible diagnosis and verification. |
| license | Apache-2.0 |
| metadata | {"author":"Holoscan Team <holoscan-team@nvidia.com>","compatibility":"holoscan-cli>=4.5.0","github-url":"https://github.com/nvidia-holoscan/holohub","tags":["holoscan","holohub","debugging"]} |
Turn one concrete wrapper failure into a minimally fixed, reproducible passing command with focused regression proof.
Require:
./holohub
command;Route non-failing app development to holohub-app-lifecycle, non-failing
Module work to holohub-module-lifecycle, and first-time SDK installation to
holoscan-setup. If the matching skill is unavailable, preserve the handoff
context and name the skill to install. Do not manufacture a failure.
The affected checkout's AGENTS.md, local help, exact reproduction, schemas,
and source are the live technical authority where they do not conflict with
user, system, or safety constraints.
If the request is planning-only or forbids execution, do not begin the steps below. Return only the proposed diagnostic order, evidence, approval boundaries, and proof requirements; do not run commands or change files, caches, artifacts, privileges, or environments.
version --json, env-info --json, relevant env-check --json,
and status --json, reviewing sensitive values before sharing.clear-cache or test --clear-cache, review
the resolved affected paths and obtain explicit user authorization before
reproduction; receiving a failing-command report is not approval for cache
cleanup. For a hang, preserve
all effect-bearing arguments but enforce an external timeout derived from
the recorded hang boundary; record the deadline, termination signal, exit
status, and whether child wrapper or container processes remain. If it no
longer reproduces, compare revision, state, inputs, image, cache,
display/devices, and environment, then report the mismatch rather than
inventing a fix.clear-cache scope, review every resolved
path, and obtain explicit user approval before clearing those paths.test <module> is not module-scoped. Run
git diff --check.If the failure does not reproduce, report the state mismatch. If it belongs to a non-failing app or Module workflow, preserve the reproduction context and route it to the matching lifecycle skill.
holohub-app-lifecycle.sudo ./holohub. Obtain approval for host packages, host-local
execution, root containers, devices/capabilities, debugger attachment, core
dumps, or permission changes.Return the exact reproduction, environment and revision, primary layer, root cause, useful rejected hypotheses, minimal fix, passing proof, focused tests and artifacts, remaining uncertainty, and final worktree state.
For a planning-only request, return the proposed diagnostic order, evidence, approval boundaries, and proof requirements without claiming execution.